Skip to content
Afterglow Docs

Multilingual text

Many fields in the Backoffice and in Practice let you write the same text in every language the app supports. App users then see the version that matches the language they chose on their phone.

This is separate from Translations, which customizes the built-in wording of the app itself. Multilingual text is for your content — module titles, article headlines, circle names, and similar.

What you see

Section titled “What you see”

A multilingual field looks like a normal text box with a language tab for each platform language, shown inside the field as a short code:

  • EN — English
  • DE — Deutsch
  • FR — Français
  • ES — Español

Switch tabs to write or review each language. A checkmark appears on every language that already has text. While you are typing, a next language hint below the field points you to the next empty tab and shows how many languages are filled.

Auto-translate missing languages (the sparkle button) fills every empty language from the one or more languages you already wrote. You can edit the suggested text before you save.

How app users see the text

Section titled “How app users see the text”

Users pick their language in the mobile app. They automatically see the matching version of your text. If their language is empty, they see the English version instead. If English is empty too, they see the first language that has text.

Required names and titles

Section titled “Required names and titles”

Required name and title fields need text in at least one language before you can save. You do not have to fill every tab.

Languages you leave empty fall back to English (or the first language that has text). Use Auto-translate missing languages if you want the other languages filled for you.

Optional fields

Section titled “Optional fields”

Optional fields — subtitles, descriptions, button texts, and similar — give you these choices:

  • Leave the field empty — nothing is shown for that field.
  • Fill just one language — every app user sees that same text, regardless of their language.
  • Fill some or all languages — users see the version in their language. Users whose language is empty see the English version instead.

You can leave any tab blank; there is no completeness check on optional fields.

Section titled “Consent documents”

Workspace documents (consent forms, terms, and similar) follow the same rules as other fields: the title and the accept and decline button texts need at least one language, and everything else is optional.

Once someone has signed a document, its text is locked. You can still turn the document active or inactive, but you cannot change the wording.

Existing single-language text

Section titled “Existing single-language text”

Text that was written in only one language before language tabs arrived still works as it is. You do not have to fill the other languages.

Where it appears

Section titled “Where it appears”

You will see this field in the Backoffice. On content pages, Practice uses the same field.

Content management (Backoffice and Practice)

  • Module, category, lesson, and step names
  • Subtitles and body texts
  • Next-page button labels
  • Survey questions and answer options

Elsewhere in the Backoffice

Section titled “Related topics”
  • Translations — Customize the built-in wording of the mobile app.
  • Content Management — Where most content names and titles are edited.
  • Content — The same content tools in Practice.