Manage localization using the admin console

You can find background information on localization in PingOne Advanced Identity Cloud in Localize tenant admin console and hosted pages.

Manage language sets

To localize the Advanced Identity Cloud admin console and hosted pages, create a language set for each locale you want to support. Each language set needs to contain translation key/value pairs that override the default phrases.

In the Advanced Identity Cloud admin console, go to touch_app User Experience > Languages, then perform the following actions:

To add a new language set:
1. Click add Add Language.
2. In the Add Language modal:
  1. Select a language from the Language list. For example, German (de).
  2. Click Add Language.
3. Follow the instructions in Edit a language set from step 3 onwards.
To import a language set, follow the instructions in Import a language set from step 2 onwards.
To edit a language set, follow the instructions in Edit a language set from step 2 onwards.

To perform contextual actions on a language set, click its ellipsis icon (more_horiz) to open its overflow menu:

To make a language set the default language set, click Make Default. This also activates the language set if it isn’t already active.

When a language is set as the default, the platform uses it for any untranslated keys in other language sets. You should therefore ensure that the default language set is as complete and accurate as possible. Any missing translations in the default language set fall back to the built-in English definitions.

To export a language set, click file_download Export. The exported file is a JSON file that contains the translation key/value pairs for the language set. The file name is in the format <language_code>.json, for example, de.json for German. The file format is compatible with the import feature, so you can use it to import the language set into another environment or keep it as a backup.
To import a language set, click file_upload Import, then follow steps 4 and 5 in Import a language set.
To deactivate an active language set, click power_settings_new Deactivate.
To activate a deactivated language set, click power_settings_new Activate.
To delete a language set, click delete Delete, then in the Delete <Language>? modal, click Delete again.

You can also access the overflow menu from the top right of the language set editor.

Import a language set

The import feature lets you import language sets from a JSON file to quickly bulk-update translations:

Compatible sources: You can use a file exported from another tenant environment or a backup file from an earlier export. If you manually update an export file or create your own file, ensure that the JSON follows the Language set format.
Matching keys: Only recognized keys are updated. Unrecognized keys are ignored (except for custom translations).
Partial updates: Only keys included in the JSON file are updated. Omitted keys remain unchanged.

To import a language set:

In the Advanced Identity Cloud admin console, go to touch_app User Experience > Languages.
Click file_upload Import to open the Import modal.
Select a language set from the Language list. For example, German (de).
Click attach_file Select file to select a JSON file that contains the translation key/value pairs for the language set.
Click Import.

Edit a language set

To edit a language set:

In the Advanced Identity Cloud admin console, go to touch_app User Experience > Languages.
Review the Languages page to find the language set you want to edit, then click it.
In the language set editor, use the vertical menu to select a section heading (Global, User, Login, Pages, Governance, or Custom translations):
- To quickly find a section heading that contains specific translation keys, enter a search term in the Search sections field above the vertical menu.
- Review the status indicators next to translation key groups and nested translation key groups:
  - Red: Contains no translations.
  - Yellow: Contains at least one completed translation.
  - Green: All translations are completed.
- Select a translation key group or nested translation key group to load its keys into the editor area. For example, under the Global section heading, select the Common translation key group (common) or select its nested translation key group Validation (common.validation).
(Optional) Filter or refine the translation keys displayed in the editor area:
- Enter a search term in the search Search keys or values field to filter by specific keys or translated text.
- Select an option from the status filter list: All, Missing, or Translated.
In the Value column, enter or update the translated text for each translation key:
- To assist with translation, select a language from the Compare to list in the table header to display reference translations alongside your current language set.
- If a value is left blank, the platform automatically falls back to the default language set.
To add custom translations for unlocalized phrases, server messages, journey nodes, or custom UI elements:
1. In the vertical menu, select Custom translations.
2. Click the Add icon (add) to the left of the search Search keys or values field.
3. In the Add Custom Translation modal, configure the following fields:
  - Current Language Value: Enter the untranslated text as it appears in the UI. For example, First Name.
  - Translation Key: Review the automatically generated key name. For example, FirstName.
  - <Language> Value: Enter the translated phrase for your language set (for example, Vorname for German).
4. Click Create Translation.
Click Save to apply your changes. You can navigate between sections and edit multiple keys before saving.