Skip to main content

Translate statements and templates

Offer your assessments in more than one language, and keep those translations current when the English changes.

Checked 12 November 2026

Who this is for​

Account administrators (to choose the languages) and anyone holding the account's translation permission (to write the translations). The translation permission is not part of any built-in role, so an account administrator needs it added through a custom policy before they can use the Translations page.

The order matters​

Two settings pages.

  1. Languages: choose which languages this account offers. With none enabled, the language switchers are hidden, so participants are not offered a choice.
  2. Translations: author the actual text. You can write translations for any supported language, but participants are only offered the languages enabled here.

Both are in the sidebar for anyone holding either the account-modify or the translations-manage permission, but each page only works with one of them. Saving Languages needs account-modify. Everything on Translations needs translations-manage.

Step 1: enable languages​

Open Languages. Tick each language you want to offer; English is marked base / source and is what everything is translated from. Choose Save languages; Cancel reverts unsaved ticks.

Choose Primary beside one enabled language to make it the account's primary language. Messages go out in the primary language beside English when the recipient has not said which language they read, and it is the language participants see when nothing else decides. Only an enabled language can be primary. If you turn the primary language off, the next enabled language becomes primary.

Enabling a language does not create any translations. It makes the language selectable: in the in-app switcher, on public campaign pages, and in the assessment taker's header. Untranslated content falls back to English.

Step 2: translate​

Open Translations. The page has three tabs (Statements, Templates and Campaigns). Statements and Templates share the same shape: a row of target-language buttons, a To translate (n) / Translated (n) pair of tabs, a search box, and a coverage badge reading "n/total translated" for the selected language. Campaigns has the language buttons and search box, and a badge reading "n/total started".

Statements​

Action statements are single reusable pieces of content, translated once and reused wherever they appear.

On the To translate tab, each row shows the statement id and the English text with a box underneath. Either type the translation and choose Save, or choose Machine translate to draft it first and then edit before saving. With no provider configured for the environment, Machine translate does not fail silently: it fills the box with the English source text and says so: "Machine translation isn't configured (no provider), showing the source text."

On the Translated tab, each row is badged with its source: authored, ont (text supplied by the ontology, the upstream source of the statement) or machine. Edit and Save as needed. A machine draft also offers Promote to authored, which accepts the draft as-is and re-badges it, and every row offers Delete.

Templates​

Templates carry a whole SurveyJS body, so the editor works differently. Choose between two modes with the Structured / Raw JSON toggle:

  • Structured: a field-by-field editor over the template's strings, including the labels and options of custom fields. MT machine-translates one string at a time, and Reset all to English puts every field back to the English source. This is the mode to use.
  • Raw JSON: the localized body as JSON, for surgical fixes. Load English body to translate seeds the editor from the current English; Reset to base replaces the editor contents with the current English again. Invalid JSON, or a body that adds, drops or renames a question, is refused with the error shown under the box.

Save with Save localized body (in Raw JSON on the Translated tab the button is just Save). There is no machine translation of a whole template body.

Campaigns​

Translate the five pieces of text on a campaign's public page: Name, Description, Instructions, Closed message and Archived message. Each field is translated on its own, and a field left empty shows in English. Instructions and the two messages may contain HTML: keep the tags and translate the words between them. Save and Delete work per field.

Keeping translations current​

When the English template changes after a translation was saved, the translated row is badged Stale: needs review in amber, with the note "The base template changed after this translation was saved. Re-sync from the base body or review the strings."

Work through stale rows by reviewing the strings in Structured mode, or by resetting to base and retranslating.

Statements have no equivalent staleness badge: the coverage count is what tells you whether new statements have appeared.

What participants see​

  • Assessment content is served in the participant's chosen language. The taker page shows a language switcher in the header when more than one language is enabled. Changing it redraws the questions in that language and keeps the answers given so far.
  • Public campaign pages carry the same language selector.
  • Interface chrome (the dashboard's buttons, banners and status pills, and the headings and buttons on participant pages) is not translated by this workflow. Its wording ships with the product: French is built in, and other languages show the English wording. Changing it is a product change, not a translator task. The questionnaire's own navigation is handled the same way: SurveyJS localises Next / Previous / Complete itself from the language the respondent chose, so a French taker reads Terminer without anyone translating it here.

Limits and gotchas​

  • English is the source. There is no way to author in another base language.
  • Machine translation is a drafting aid: its output is badged machine until a human saves or promotes it, so you can always tell which is which.
  • Deleting a translation returns that content to the English fallback rather than breaking it.