Portal journey languages
Use this procedure to choose the languages the people you invite through Portal access links may use, and to adapt the wording of their journey. Content was checked on 2026-10-09 against portal-fe 2563ceb and portal-be 9dae623, and observed in DEV on 2026-10-18 (portal-fe 00ea9a6, portal-be 9ad5ae3) with a synthetic company: the administrator published version 1 with custom wording that the recipient's page then showed, an HTML tag was refused with HTML tags are not allowed., and a profile without administrator access saw the page read-only while the service refused its change. On 2026-10-22 the fields, actions and messages below were checked against the Portal interface source (portal-fe 01e16b4); those details are not observed.
Who may do it
Only a company administrator can publish. Everyone else with access to Portal can open the page and review the settings; they see Only tenant administrators can change journey languages and texts. You can review the settings here., and the service refuses their changes.
Before you start
- Until the first publication the page shows Never published: the standard settings apply.
- Each publication creates a new version. Links already sent keep working; the version a recipient reads depends on the setting Pin complete bundles for new links (step 4).
Steps
- In Portal, open Send & Collect › Journey languages. The page reads Loading journey languages…, then Choose which languages your invited visitors can use and adapt the wording of the journey for each of them.
- Under Languages offered to visitors, tick the languages to offer: English, Português (Brasil), Português (Portugal). At least one is required.
- In Default language, choose one of the enabled languages. It is used when neither the link nor the visitor's saved preference decides. With more than one language enabled, people who create links can also fix the language of each link, and recipients see a Journey language selector.
- Pin complete bundles for new links — when ticked, each link created after this publication keeps a fixed copy of the journey: later changes to the form or the wording do not reach it. Applies only to links created after this setting is published. Existing links stay unresolved.
- Under Custom wording, choose the Language being edited. For each message, the Standard text is shown; type Your text to replace it, or leave it empty to keep the standard. Keep every placeholder in braces exactly as shown, and stay within the length shown for the message. Security and consent notices cannot be changed: Security and consent notice — only the standard text is shown to visitors.
- Check the result under Preview, choosing the Preview language.
- Select Publish. The button shows Publishing…; Journey languages published as version … confirms it.
Follow the results
- Outcomes by language counts each link once, by the language the recipient actually saw: Started, Completed, Abandoned, In progress, Revoked.
- Journeys with errors counts links with errors reported from the recipient's page, per language.
If something goes wrong
Nothing was published. Fix the highlighted fields and try again. — nothing changed. The highlighted field says why. When the fields to fix are in a language other than the one on screen, Other languages also have fields to fix: names them, with a button to switch to each.
Nothing was published. Check your connection and try again. — nothing changed, and no field was refused: the page could not reach the service. Select Publish again.
| Message | What to do |
|---|---|
| Enable at least one language. | Tick a language. |
| The default language must be one of the enabled languages. | Change the default, or enable that language. |
| There is custom wording for a language that is not enabled. | Enable the language, or clear its custom wording. |
| The placeholders must be the same as in the standard text. / A placeholder brace is missing or misplaced. | Copy the placeholders from the standard text exactly. |
| The text is longer than allowed. | Shorten it. |
| Line breaks are not allowed. / HTML tags are not allowed. | Use plain text on one line. |
| Security and consent notices cannot be customized. | Clear the custom text of that message. |
| Only tenant administrators can publish journey languages and texts. | Ask a company administrator to publish. |
| This language is not supported. / This language is listed twice. | Reload the page and choose the languages again. |
| This message is not part of the journey. | The message was removed from the journey; reload the page. |
| The custom text is empty. | A custom text saved as empty before emptied fields were treated as "standard text". Clear the field again and publish: an empty field is no longer sent. |
| The journey languages could not be loaded. | Select Retry. |
A message about custom wording appears under the text box it concerns, which gets a red border; other messages are listed above the form. Messages about the wording of a language other than the Language being edited are not shown: switch the Language being edited to find them.
Field reference
| Field | What it does | Required | Format / values | Default |
|---|---|---|---|---|
| Languages offered to visitors | The languages recipients may use | At least one | English, Português (Brasil), Português (Portugal) | As last published |
| Default language | Used when neither the link nor the visitor's saved preference decides. | Yes | One of the enabled languages | As last published |
| Pin complete bundles for new links | Freezes the journey of each link created afterwards. Applies only to links created after this setting is published. Existing links stay unresolved. | No | Box | Not ticked |
| Language being edited | Which language's wording the text boxes show | — | One of the enabled languages; works also in read-only mode | The first enabled language |
| Your text (one per message) | Replaces the standard text of that message. Leave a field empty to keep the standard text. Placeholders in braces must stay exactly as shown. Emptying a field removes the custom text, so the standard text comes back with the next publication. | No | Plain text on one line, up to the length shown (Up to … characters), with the placeholders listed (Placeholders: … or No placeholders) | Empty |
| Preview language | The language the Preview shows. What the visitor reads in the selected language, with your wording applied. The form name appears as KYC and dates as today. | — | One of the enabled languages; works also in read-only mode | The first enabled language |
Unticking a language moves the Default language and the Language being edited to the first language still enabled. Its custom wording is kept and sent with the next publication.
| Button | What happens | Who can use it | Reversible? |
|---|---|---|---|
| Publish | Publishes everything at once as a new version; reads Publishing… meanwhile. Nothing is published if any field is refused. | A company administrator | Publish again with the previous settings; there is no undo |
| Retry | Loads the page again after The journey languages could not be loaded. | Everyone | — |
| Area | Content |
|---|---|
| Header | Version …, or Never published: the standard settings apply. |
| Outcomes by language | Counts each link once, by the language the visitor actually saw. Website visits are not included. Columns Language, Started, Completed, Abandoned, In progress, Revoked. No visitor has opened a link since language recording began. when empty; Visitor metrics could not be loaded. on failure. |
| Journeys with errors | Counts distinct links with reported errors. Translation version not recorded. Columns Language, Affected journeys. No visitor errors have been reported. when empty; Error metrics could not be loaded. on failure. |
Last reviewed 2026-10-18 · Version 1.0.0 · Owner: product-documentation