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.
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.
- 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:
| 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. |
| The journey languages could not be loaded. | Select Retry. |
Last reviewed 2026-10-18 · Version 0.2.0 · Owner: product-documentation