Localization
Translate questionnaires, step titles, descriptions, and other UI texts directly within the Configuration builder so end-users see the verification widget in their preferred language.
How localization works
Prerequisite: the Language step
Purpose: Localization only becomes available once a Language step is added to your configuration. This step defines which additional languages users can choose from during verification.
Tip: Add the Language step first, then come back to translate your content — if no Language step exists, the builder behaves as single-language and the language selector won't appear.
The language selector
Purpose: Once a Language step exists, a selector appears at the bottom of the Configuration builder, letting you choose which language you're currently editing content for.
How it works:
The selector is visible at all times, no matter which step or section you're working on
Your default language (set in Configuration settings) is always listed first and pre-selected
All other languages you've added via the Language step appear below it
Use the search field to quickly find a language in a long list
Click Add more to jump to the Language step and add or remove available languages
Tip: Think of the selector as a "which language am I typing in right now" switch — it applies to every translatable field in the builder: step titles, descriptions, questionnaire titles, questions, options, and prefilled answers.
Editing modes
Default language — full editing
When the default language is selected, you have full control over your configuration:
Add or remove questions and options
Edit structure and keys, adjust step parameters.
Edit all titles, labels, and descriptions
This is your "source of truth" — all translations reference back to whatever is written here.
Translation language — translation-only mode
Purpose: When you switch to any non-default language, the builder enters a restricted translation-only mode, so you can safely add wording without accidentally changing the structure of your flow.
What happens:
Every text field shows your default-language text as a placeholder, so you always have the original to translate from
Structural editing is disabled — you can only edit text, not add, remove, or reorder anything
Tip: If you need to restructure anything (add a question, remove an option, etc.), switch back to the default language first — translation mode is purely for wording.
If your configuration has errors
If you try to enter translation mode while your configuration has unresolved errors, you'll see a "Fix errors before translating" prompt asking you to resolve them first.
Tip: Resolve validation errors in the default language before starting translation work, to avoid this interruption.
Saving translations
There's no separate "Done" button for translations — everything is saved using the main Save button, just like your default-language content.
You can translate as much or as little as you like:
Only languages you've actually edited are stored
Only fields you've actually translated contain that language's text
Partial translations are completely fine — nothing needs to be "complete" before saving
How the widget displays translations
Purpose: Controls what an end-user sees when they use the verification widget in their selected language.
How it works:
If a translation exists for the user's language, it's shown
If a translation is missing for a specific field, the widget automatically falls back to the default language for that field only
Partial translations never cause errors — users simply see a mix of translated and default-language text where needed
Changing your default language later
If you change the default language after content already exists, the system automatically remaps your existing content to the new default language key — and never overwrites content that already exists under that key. This makes it safe to change your default language without losing translated work.
Last updated
Was this helpful?