Translations

Translations lets you offer multiple languages on your program website. Members pick a language from the header language menu (when enabled), and UI labels—sign-in fields, buttons, Design Studio default text, and similar strings—display using your translated values.

This guide covers language setup, the translation dictionary, and program-wide language defaults. It does not replace Articles or Pages for long-form content you write in a single language.

Overview

From Settings → Translations you can:

• Register languages your program supports (from a built-in language list)
• Set each language to Active or Inactive
• Maintain a dictionary of English keys and translated values per language
• Choose a default language and optionally hide the language selector on the member site

Translations screen tabs

Where to find it

• Route: /translate/{programId}
• Side navigation: Settings → Translations

Page subtitle in the admin: Add translations here that your program members can select when using your program website.

Active languages appear on the member site when you include a Menu Bar in Design Studio and at least one language is Active. English is always listed in the selector when other active languages exist.

Prerequisites

• An open program with program administrator access
• Editor role (or higher) — required to add, edit, and delete languages and dictionary entries
• A Menu Bar (or equivalent header with the language control) on published templates in Design Studio, if you want members to switch languages on the live site

Languages list

The Languages tab shows a searchable table:

Click new to add a language, or click the language name to open the edit dialog.

Only Active languages are offered to members on the program website. Inactive languages stay in the admin for editing but are not selectable on the live site.

Step-by-step

Add a language

1. Open Settings → Translations → Languages tab.
2. Click new.
3. In the dialog, choose Language from the dropdown (code, English name, and native name—for example FR - French (français)).
4. Choose Status — Active or Inactive.
5. Click Save.

If that language is already registered, you see an error such as Language is already registered.

Add and edit dictionary entries

After a language exists, open it to maintain translated strings.

1. On Languages, click the language name (or Edit in the actions menu).
2. The dialog widens and shows a table with English, Translation, and Actions.
3. Click new to add a row:
   • English — The source UI string (must match the English text used in the app exactly).
   • Translation — The text members see when that language is selected.
4. Click Save on the language dialog to persist the language record and its directory (dictionary) to the program.

To change an entry, use Edit on the row. To remove an entry, use Delete on the row, then Save the language dialog.

Duplicate English keys in the same language are rejected when you add or rename entries.

Activate or deactivate a language

1. Open the language edit dialog.
2. Change Status to Active or Inactive.
3. Click Save.

Members only see Active languages in the site language menu.

Delete a language

1. On Languages, open the row Actions menu → Delete.
2. Confirm in the delete dialog.

Delete is disabled while the language still has dictionary entries (the Translations count is greater than zero). Remove or move entries first, then delete the language.

Set default language and selector visibility

1. Open Settings → Translations → Settings tab.
2. Default language — Choose the locale members see on first visit (includes EN - English plus languages you added on the Languages tab).
3. Hide translate selector — When checked, stores a program flag to hide the language picker (configure alongside your header in Design Studio).
4. Click Save.

The default language is stored on the program and applied on member flows such as account activation and password reset, together with loaded dictionary data.

How translations appear on the member site

After changing dictionary entries or default language, members may need to refresh the site or switch language again to see updates.

Tips and limitations

• Editor role required — Viewers can open the list but cannot add languages, edit dictionaries, or delete languages.
• Match English keys exactly — The English field must match the source string in the product (case and punctuation). If a label does not change on the site, the key is likely missing or misspelled.
• Inactive vs delete — Use Inactive to hide a language temporarily; delete only after clearing dictionary rows.
• English in the selector — When any non-English language is active, English remains available in the member language menu.
• Demo programs — new, Save, and Delete are disabled on demo programs.
• Not for Terms/Privacy HTML — Legal pages are edited on the Terms and Privacy tabs; link them from registration and menus as needed.
• Transactional email — Some backend messages respect the program default locale (for example French when default is fr); confirm critical emails after changing default language.

Related

• Overview — Other Settings areas (Website, Terms, Privacy)
• Website — Sign-in and registration (labels can be translated)
• Titles — Program name on sign-in pages
• Design Studio — Menu Bar and member site layout
• Menus — Navigation labels may use translatable defaults
• Members — Member-facing experience after language setup
• Programs — Open program and preview live site