Configure Board Settings

On the Board Settings | General screen, you can configure the following options:

On the Board Settings | Profile screen, manage your user profile, including your name, work email, module contact preferences, and notification settings.

Notification Settings

Configure your notification settings to control the updates you receive.

• Delivery channel - Select where you receive system notifications by default:

  • Default communication channel - Receive system notifications by the default communication channel set by your admin. This may be email or a chat app like Slack.

  • Only Email - Only receive system notifications by email.

  • Unsubscribe from all notifications - Do not receive any notifications from Tonkean.

• Workflow notifications - Select where you receive workflow notifications (for example, notifications for reviewing or approving requests):

  • Receive workflow notification to Tonkean Slack App - Receive notifications from the Tonkean Slack App in your Slack instance (the sender is "Tonkean").

  • Receive workflow notification to the Slack Bot - Receive notifications from the default Slack Bot.

  If you don't have Slack connected to your Tonkean instance, these settings are ignored.

• Scheduled notifications - Configure your scheduled and recurring notifications:

  • Morning alerts - Receive a daily summary of important events through your chosen delivery channel.

  • Scheduled reports - Receive period reports through your chosen delivery method.

• Locale - Set your locale, determining your language, region, and date/time format for localization purposes.

On the Board Settings | Permissions screen, you can set board admins, access for Tonkean Support, and control who can publish solutions.

Set Default Actor

The default actor is automatically assigned as the user responsible for creating the module item and for the actions in the module. For example, if you set the Updater to Default actor in an Update Field action, that user displays as the one who performed the action in the relevant business report and logs.

The default actor is automatically set to the module creator.

Enable Support Access

Enable support remote access to allow Tonkean support to view and edit the module for support and troubleshooting needs. All actions and changes performed by support are logged.

For modules whose permissions are not set to Private, the support access setting is inherited from the board settings. To configure support access in the board settings, select your profile icon in the upper right and select Board Settings. Select Permissions in the sidenav and then enable or disable the support access as needed.

Configure Solution Publish Settings

By default, any maker with access to a solution can publish that solution. Configure the provided checkboxes to restrict who can publish a solution:

• Admin controls who can publish - Enable additional options for managing who can publish a solution. By default, this option is disabled, allowing any maker to publish solutions. Enabling this option requires you to specify which users can publish solutions by selecting the settings button on the Solutions Studio screen, , then navigating to Manage Publishers and adding publishers.

• Restrict solution creation only to board admins - Restrict who can create a new solution exclusively to board admins.

Set Invite Settings

Enable this option to allow users to set owners and collaborators outside of their board. Once enabled, these outside users are invited to the board and given access to any public modules.

On the Board Settings | Theme screen, you can set a company logo, homepage background image, and brand colors. You can also set global colors to set a brand-aligned color palette.

Once these elements are set, you can apply this theme globally for your entire board, ensuring a consistent look and feel across all your solutions. Enabling this global theme replaces any custom themes set at the level of individual workspace apps, forms, or interfaces, and prevents makers from setting custom themes.

To enable the board-level global theme, select the Apply globally toggle.

To configure your board theme, follow the steps below. As you make changes to your theme, view the Preview Theme panel on the right and select the different platform areas to see how the theme colors and elements display.

All settings are optional.

Tonkean provides the ability to translate and localize process contributor-facing experiences. Leveraging the react-i18next standard, Tonkean's translation feature is powered by language and region-specific JSON files you can upload to support specific locales, or download to customize as needed.

In addition to left-to-right languages like Spanish and German, Tonkean also supports right-to-left languages like Arabic and Hebrew, as well as the localization of date and number formats.

Multi-language interactions in the AI Front Door and with agents are supported based on the capabilities of the integrated AI service (for example, OpenAI or Anthropic). In most cases, major languages like English, Spanish, and German are supported with high quality, whereas less common languages or regional variants may provide mixed results. We recommend additional testing for these use cases.

On the Board Settings | Translations screen, you can manage translations of end-user-facing interface elements like field labels, button text, and descriptions. This feature does not include translation of the solution-building experience for makers. These areas of the platform will always be in English. Similarly, notifications sent to shared channels (where the recipient's locale is unknown) are not localized.

The entire end-user experience can be localized to the user's native language, but the content entered into that experience will be in the language entered and will not be translated.

To enable translations on your board, select the Enable translations toggle.

Add and Manage Locales

Locales are language and country-specific entities with associated JSON files containing translations of relevant text in your Tonkean solutions. For example, the locale for American English would be English (United States) with the resource file, en-US.json, while the locale for Australian English would be English (Australia) with the JSON file, en-AU.json. You control and update the translations for your solutions by managing these locales and their associated JSON files.

Relevant areas of the platform and your solutions are automatically localized and translated based on the Locale selected by the user on the Board Settings | Profile screen.

Translate JSON Resource Files

You are responsible for the translation of your resource files. There are some free utilities available, such as this i18next translation tool, as well as paid services like locize. We recommend using an enterprise-grade Translation Management System, such as Lokalise, Crowdin, or Smartling, which are optimized for i18next and have powerful features such as workflow management, translation memory, and automations.

For each locale you want to translate, you must create a specific resource file following the i18next naming conventions; that is, de-DE.json, es-MX.json, zh-CH.json, and so on. Tonkean requires both the language and locale to display the appropriate date and number formats. For more information about language codes, see this i18next FAQ. Iana also provides a list of language tags.

While the ultimate responsibility for accurate translations is on the customer, Tonkean offers free machine translation upon request. This provides a baseline for each language, making the effort one of reviewing and correcting rather than needing to translate all strings from scratch.

To request machine translation, contact your customer success manager or, if engaged with one, your Implementation Architect.

Add and Manage Common (Board) Locales

Common locales control the translations for all common experiences at the board level, including text on the homepage, board-level settings screens, menus, and so on. The US English locale is set as the default for the common level.

When translations are enabled, an additional button displays in the solution publishing window labeled Create translation version. See Create a Solution Translation Version. Selecting this button (instead of Publish) to generate the en-US.json file containing every string in the solution. This file is the foundation for creating additional locales described below.

To add a locale, follow the steps below:

1. Select Add locale in the upper right. The Add Locale window displays.

   

2. Select Browse Files to select a file, or drag and drop a resource JSON file from your local machine, then select Save.

   

3. Your new locale is added with its associated resource file, and you can test it by navigating to your Profile and toggling your locale to the one you added.

   

Add and Manage Solution Locales

Solution versions control the translations for all solution-level text, including field labels, interface text, button text, and so on. Makers in the relevant solution can create a solution translation version, which generates a default resource file for the solution in a base language.

For example, a translation version and accompanying locale for English (United States) was made for the Tonkean Maker Course solution:

Once you have translated the en-US.json file into the desired languages (e.g., de-DE.json, zh-CN.json), it's time to add those translated JSON files to the solution as new locales. To create a new locale from this default resource file, follow the steps below:

1. Select Add locale in the upper right. The Add Locale window displays.

   

2. Select Browse Files to select a file, or drag and drop a resource JSON file from your local machine, then select Save.

   

3. Your new locale is added with its associated resource file, and you can test it by navigating to your Profile and toggling your locale to the one you added.