Skip to main content

Configure multilingual login pages

When the login page language selector offers all available locales but your organization only operates in a subset of those languages, users may select a locale that is not relevant to your deployment. Restricting the language selector to only the locales your organization uses keeps the experience clean and focused.

IDaaS already provides translations for all default strings in every supported locale. Language restriction is about limiting which locales appear in the selector, not about providing missing translations.

Before you begin​

  • You have a Site Administrator role with permission to modify customization settings.
  • You know which locales your organization operates in.
  • Optional: If you have customized login messages, you have prepared overrides for each enabled locale. See Customize login page text and messages.

Restrict available languages​

Limit the language selector on entry pages to only your supported locales.

  1. Go to > Customization > Theme.
  2. Select the Custom Theme tab.
  3. Expand the Login Layout and Flow section.
  4. Set Restrict Language Selectors to Enable.
  5. In the language list that appears, select the checkboxes for each locale your organization supports.
  6. Click Save.

Only the selected languages appear in user-facing language selectors on login, password reset, registration, and logout pages.

Understand fallback behavior​

When language restriction is enabled and a user's browser or authentication context requests a locale that is not in the enabled set, IDaaS falls back to the account's default locale. This ensures users always see a fully translated page rather than a partially translated or untranslated one.

Provide custom messages per language​

IDaaS already provides translations for all default strings, so the login pages work correctly in every enabled locale without any overrides. If you have customized login messages (for example, organization-specific terminology or helpdesk contact information), ensure those overrides are applied in each enabled locale so your custom wording is consistent across languages.

  1. Go to the Custom Messages tab.
  2. Select the first enabled locale from the language drop-down.
  3. Export the strings as JSON, apply your custom wording, and import the updated file. See Bulk edit with import and export for detailed steps.
  4. Repeat for each enabled locale.
tip

Use the customization count badge on each locale in the drop-down to confirm that all locales have a consistent number of overrides. A locale with fewer customizations than others may indicate that your custom wording has not been applied there yet.

Supported locales​

For the full list of locales that IDaaS supports for custom messages and language restriction, see IDaaS supported languages.

Verify the experience​

Confirm that the language restriction works correctly.

  1. Open a private browser window.
  2. Navigate to your tenant login page.
  3. Confirm that the language selector only shows your enabled locales.
  4. Change your browser language to a locale that is not in the enabled set.
  5. Reload the login page and confirm it falls back to the account default locale rather than displaying the unsupported language.

Next steps​