Translations

The Translations feature assembles text inputs from your Strivacity instance, such as your brand's proprietary communications, consent texts, attribute error messages, and more, into a downloadable content package. You can use these packages to create localized experiences for customers by translating content into supported languages.

Translations collect your input content from the following places in the Admin Console:

Account attributes
- Display names
- Display names for options in Select type attributes
Branding policy contents
- Copyright text
- Support text
- Additional contents
- Additional texts for every customer experience
Consents
- Display text
- Self-service display text
Identity verification policies
- Identity verification notification display
- Failure message
- Data collection display message
- Data collection fields' display name
Notification policies
- Email notification subjects and text bodies
- Text message bodies

🚧
Some parts of the UI messaging (such as button labels and standard error messages) are not included in the content package. These are built-in translations that Strivacity provides for the customer experience in supported languages and cannot be modified through the Translations feature. To customize these sign-in experience texts, refer to the Branding policy documentation.
You can also apply translations at the code level using Lifecycle event hooks. In certain hooks, you can retrieve the language associated with the current account and return translated content based on it, enabling fully dynamic, language-aware responses.

Default translations for new instances

Newly created Strivacity instances include built-in translations for all default customer-facing content, including UI labels and standard messages. These are available for all supported languages, even before you upload a custom content package.

If a customer-facing element hasn't been modified in your Admin Console, Strivacity will automatically apply the default translation for that content in supported languages.

📘
Built-in translations are applied in the background and aren't visible in exported content packages. Only custom changes appear in downloads.

Default supported languages

Strivacity supports translation import and display of the following languages for the customer experience:

Arabic (Egyptian)
Chinese (China)
Chinese (Hong Kong)
Kabuverdianu (Cape Verde)
Haitian Creole (Haiti)
Danish (Denmark)
Dutch (Netherlands)
German (Germany)
Estonian (Estonia)
English (Canada)
English (UK)
English (United States) Default
Finnish (Finland)
French (Canada)
French (France)
Hungarian (Hungary)
Italian (Italy)
Japanese (Japan)
Korean (South Korea)
Latvian (Latvia)
Lithuanian (Lithuania)
Norwegian (Norway)
Polish (Poland)
Portuguese (Brazil)
Portuguese (Portugal)
Russian (Russia)
Somali (Somalia)
Spanish (Spain)
Swedish (Sweden)
Thai (Thailand)
Turkish (Türkiye)
Ukrainian (Ukraine)
Vietnamese (Vietnam)

Display language precedence

📘
The Admin Console itself is available in US English only. Language selection applies to the sign-in experience and customer-facing journeys.

Before any explicit language selection is made by customers at sign-in, the login session collects information and goes through a series of checks to determine the display language of the customer experience. If the content package is enabled for the selected language, then the UI and complementary texts, such as brand communications or error messages, will appear in that specific language.

🚧
Brand content not translated to the preferred language also falls back to the instance default.

The display language is selected in this order:

login_hint parameter
If a login_hint is provided that includes a preferred language, and that language is enabled on your Strivacity instance, it is applied to the customer's session for that sign-in flow. The customer can still change the language during the session. If no valid login_hint language is present, the next option is checked.

The login_hint must be a JWT-encoded string containing the following payload:
```
{
	"language": {
		"force": "en-US"
	}
}
```
Identified account
If the customer's account can be identified before any interaction (for example, based on a remembered identifier, a login hint, a password reset flow, or an identity verification flow) Strivacity uses the display language stored in that account. The customer can still change it during the sign-in flow. If the account cannot be identified, the next option is checked.
User agent language preference (Accept-Language header)
If the user agent sends an Accept-Language header with a language that is enabled on your Strivacity instance, that language is applied. Once determined from the header, the preference is stored in the session, so subsequent requests follow rule 2. If no supported language is found in the header, the next option is checked.

All Strivacity-provided SDKs expose an option to set this preference directly. Refer to the documentation of your SDK for details.
OIDC ui_locales parameter
If none of the above apply, Strivacity checks for a ui_locales parameter in the OIDC request and uses it as a fallback. If the specified language is enabled and supported, it is applied and stored in the session for subsequent requests. If not available, the next option is checked.
Default language
If none of the above conditions are met, or if no preferred language is supported, Strivacity falls back to the default language configured for your instance, which is English (United States) by default. Brand content not translated to the preferred language also falls back to the instance default.

Language settings

📘
Default language configuration
The default language for each Strivacity instance is determined when the instance is created. If your organization requires a different default language, contact Customer Support to request an update for your instance.

The default language of the customer experience in Strivacity is English (United States). Every other supported language can be enabled or disabled.

If a language is disabled:

It can't be applied to customer sign-in experiences.
The language option is not available at sign-in in the language menu.
Administrators can’t select it as the language of account invitation or creation.

📘
Content packages
You can still manage and import content packages (complementary texts such as supporting texts for UI, notification bodies, or error messages) for disabled languages. This allows you to prepare translations ahead of enabling them.

Export

You can find Translations in the Instance configuration section of the Admin Console.
Select a content package. The US English package is available by default, and it cannot be disabled or imported.
Select Export. This will generate a JSON file with your custom text for that language.

📘
Built-in translations are not included in exports, only content you’ve configured is exported.

Import

Select Import translation.
Upload a JSON file that matches the structure of Strivacity export packages.

🚧
Only JSON files that follow the format of content packages previously exported from a Strivactiy instance can be imported successfully.

Updated 2 days ago