Skip to main content

Configure Board Settings

Configure the settings for your board, including permissions, notification settings, theme, localization, and more.

For other settings, see Manage Modules and Manage Users.

General

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

  • Name - The board name, visible to all users.

  • URL ID - The unique identifier for your board, used both within your organization in the uncommon scenario where you have multiple boards, and by Tonkean Support and Solution Services.

  • Statuses - Set the default statuses for all modules in this board.

board_settings_general_overview.png

Profile

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.

  • Don't send notifications to Slack bot - Enable this option to block notifications from the Tonkean Slack bot.

  • I don't want to get any emails from Tonkean - Enable this option to block emails from Tonkean.

  • A.I. Module Follow ups - Enable this option to receive automated follow-ups from Tonkean workflows.

  • Scheduled reports - Enable this option to turn on scheduled reporting.

board_settings_profile_info.png

Permissions

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

Edit Board Admins

Board admins play an important part in implementing and maintaining your organization's security and permissions policies in Tonkean. Board admins have a variety of powers:

  • Manage users and assign roles

  • Connect and configure identity providers

  • Set board-level data source connection rules

  • Set publishing and invitation policies

To add or edit board admins, follow the steps below:

  1. Select Edit Admins to add or remove board admins.

    board_admins_edit.png

  2. Search for board users to add as board admins or select the x on the relevant user to remove a user's board admin role.

    board_admins_search.png

  3. When finished, select Save.

    board_admins_save.png

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.

default_actor.png

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.

support_access_enabled.png

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:

  • Allow publishers management - 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 module settings button on the Solutions Studio screen, three_dots_horiz.png, 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.

solution_pub_settings.png

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.

invite_settings.png

Theme

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.

theme_apply_globally_toggle.png

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.

theme_preview.png

All settings are optional.

  1. To upload a company logo, select Upload. The Upload Image window displays.

    theme_company_logo_upload.png

    Select Browse Files to select an image from your local machine or paste in a web link, then select Save.

    The maximum file size is 5mb and the supported file types are JPG, JPEG, and PNG.

    theme_logo_upload_image_window.png

  2. To upload a homepage cover background image, select Upload. The Upload Image window displays.

    theme_homepage_background.png

    Select Browse Files to select an image from your local machine or paste in a web link, then select Save.

    Select an image with a 10:3 ratio; we recommend an image that's 1000 x 310px

    theme_homepage_hero_img_upload_window.png

  3. To upload a homepage cover logo, select Upload. The Upload Image window displays.

    The homepage cover logo is a logo that only displays on the Tonkean homepage. The company logo configured in step #1 displays everywhere else.

    theme_homepage_cover_logo.png

    Select Browse Files to select an image from your local machine or paste in a web link, then select Save.

    We recommend an image with a height of 80px.

    theme_homepage_cover_logo_upload_window.png

  4. To set a brand color and secondary brand color, select the relevant dropdown and choose a color.

    theme_primary_sec_colors.png

  5. To set global colors, select the relevant dropdown to overwrite an existing color or select +Add Color to add another color to the global colors set. When a theme is applied globally, users are able to select only from provided global colors.

    theme_global_colors.png

    Select the order icon, click_and_drag_hamburger.png, and drag the colors to reorder them in the set—this is the order they display in for users.

Translations

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 resource files you can upload to support specific locales, or download to customize as needed.

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 enable automatic translations for end-user-facing content 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.

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

translations_enable_translations_toggle.png

Add and Manage Locales

Locales are language and country-specific entities with associated resource files (in JSON format) 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, while the locale for Australian English would be English (Australia) with the resource file, en-AU. You control and update the translations for your solutions by managing these locales and their associated resource 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 Resource JSON Files

You determine how to translate your resource files based on your preferences—Tonkean does not provide machine translation. There are some free utilities available, such as this i18next translation tool, as well as paid services like locize. Additionally, LLMs like GPT can provide adequate machine translation for many languages.

For each locale you want to translate, you must create a specific resource file following the i18next naming conventions. For more information about language codes, see this i18next FAQ. Iana also provides a list of language tags.

To start, we recommend downloading the

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.

To add a locale, follow the steps below:

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

    translations_add_locale_select.png

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

    translations_add_locale_window.png

  3. Your new locale is added with its associated resource file.

    translations_locale_added.png

Add and Manage Solution Locales

Solution locales control the translations for all solution-level text, including field labels, interface text, button text, and so on.

In this section: