Translation manager
Customise the text shown to end users during verification flows
The Translation manager lets you replace the default text for any customisable text element in a flow version. Translations are managed per flow version and cover only the flow languages configured for that version. Changes are stored on the flow version and applied to end users at runtime.
To open the Translation manager, click Translation manager at the top right of the Flow Editor in Studio.
If no flow languages are configured for the flow, the Translation manager is disabled — to enable it, configure at least one flow supported language in the Flow Editor under Configuration (top-right button).
What can and cannot be customised
The Translation manager covers text rendered by the Player itself. Customisable text falls into two groups:
Flow-wide text — available for every flow, even if it contains only non-customisable steps. These appear in the CSV under the category Flow-wide:
- Session lifecycle screens — session expired, session aborted, session completed, technical error, generic loading, redirecting, and similar screens shown around or at the end of a session.
- Retry dialog — offered when a step supports retry.
- Quit confirmation dialog — shown when the user attempts to leave mid-flow.
Per-step text — text specific to an individual step, such as a step's loading message or status screen. These appear in the CSV under the step's name as the category. The following steps support per-step translation overrides:
- Biometric verification (v2)
- Capture IDcheck (v3)
- DocIDV (v3)
- Capture IDcheck (v4)
- eID (v2)
- France Identité
- EUDI wallet (v2)
- Verification method selector (v2)
Per-step translation configuration is not yet available for all steps. We are working on extending this support to all steps.
Downloading the CSV
Click Download current translations in the Translation manager dialog to download a CSV file containing all customisable text for this flow version.
The CSV has the following columns:
| Column | Description |
|---|---|
Category | The step name for per-step text, or Flow-wide for flow-wide text |
Screen | The screen or context within that category (e.g. retryDialog) |
Translation key | The specific text element (e.g. heading, body, confirmButton) |
| (languages) | One column per supported language, pre-filled with the current values |
The language columns contain only the languages configured for this flow version — see Language configuration. Text that has not yet been customised appears with its default text.
Character limits
| Text element | Limit |
|---|---|
| Heading | 64 chars |
| Body | 400 chars |
| Label | 50 chars |
| Button | 40 chars |
Editing translations
Edit the text directly in the CSV. A few things to keep in mind:
- Only text that differs from the default is saved as a customisation. Blank cells and cells still containing the pre-filled default text are ignored — the default text continues to apply.
Each upload merges into the existing translations — only the cells you changed are updated, everything else is left as-is. You can upload a CSV that changes a single value, or send the file to a translator for one language and upload it back without affecting other languages.
Uploading translations
Click Upload in the Translation manager dialog and select your edited CSV file.
After upload, you will be shown a review screen with a breakdown of what will change — for example, how many new translations were added, how many updated existing ones, how many values were skipped as empty, and how many already matched the current translation and will be left unchanged. Click Apply changes to save the changes to the draft version.
Reset to default translations
Click Reset to default translations... in the Translation manager dialog to discard all custom translations for this flow version and revert to the default texts. You will be warned beforehand and asked to confirm before proceeding.
Previewing before publish
Before promoting the flow version from draft to staging and beyond, use the Launch Session button in Studio to run through the flow and verify that all customised text appears as intended.
Drafting a new flow version
When you create a new version from a previous version, any custom translations from the source version are carried over automatically. The new draft starts with the same text as its origin, which you can then modify or extend.