---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Configuring System Localization

# Configuring System Localization {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the locales, languages, regions, and locations needed to accommodate your users.

## Configuration overview {#configuring-system-localization__section_overview}

The following list is a high-level overview of the workflow to get started localizing an instance. However, there may be use cases where performing these steps in a different order is preferred.

1. [Set the instance locale](https://servicenow-prod.fluidtopics.net/qydsvamt6lfEcMk8h~odaA#c_DefineLocales "Specify a locale for an instance so information such as dates, times, and currencies display properly based on your location.")

   By default, the instance locale is the United States (en.US). You should set the instance locale before a system has gone into production and not change it
   after.
2. [Activate a language](https://servicenow-prod.fluidtopics.net/JVX9OJGGemU7rGe1QNjBRw "By default, the language supported by the platform is American English. You can activate plugins for other supported languages if you have the admin role.")

   Activate any of the ServiceNow® internationalization (I18N) language plugins to get translations of base system UI strings in the languages your users need. American English is the default language and doesn't need to be
   activated.
3. [Set the default language for an instance](https://servicenow-prod.fluidtopics.net/nIsxydZg26bLdrR5cEm8jA "Change the language that appears by default for an instance.")

   Select a default language for an instance if it should be a language other than American English.
4. [Set a fallback language](https://servicenow-prod.fluidtopics.net/POLFU3TS7H6L913zN~SzJg "Set a fallback language to be used when user interface text is not translated in the user's preferred language to accommodate the language needs of your users.")

   Specify the fallback language for another language so that if UI text isn't translated in a language, the text displays in the fallback language instead. By default, if a UI string isn't
   translated in the preferred language of an instance session, it displays in English.
5. [Set up locations](https://servicenow-prod.fluidtopics.net/e5lig8dYlfvwC2II5L_w8g "If your organization supports more than one distinct location, you can configure these locations in the platform to help further identify users, assets, and incidents.")

   Configure the locations that your organization supports to help identify users, assets, incidents, and more by location.
6. [Create regions for language selection in portals](https://servicenow-prod.fluidtopics.net/8imJjBup_1qHM~HD1QYqmg "Create regions to group languages in the language selector in portal headers.")

   Map languages to regions to organize the language selector for guest users.
7. [Ensure that translated choices appear for applications added by plugins](https://servicenow-prod.fluidtopics.net/kgm3_dzHHyxp7zg1yBu6_g "Ensure that translated choices appear for applications by activating translated choice records after corresponding English choice records have been added by plugins.")

   If you activate other application plugins after having activated language plugins, translated choices in lists might not appear for the applications or features installed by their
   plugins. Ensure that translated choices appear for those applications by activating translated choice records after corresponding English choice records have been added by plugins.

{#configuring-system-localization__ol_lcw_mtz_kwb}

After you configure your instance using the localization options and supported languages, you might need to translate custom content or translate the instance to an unsupported language. For more information, see [Translating custom content](https://servicenow-prod.fluidtopics.net/YWLPbjP7kFP4Dvd8bd9ztw "Translate content you create or modify to a supported language or add an unsupported language.") and [Translating to an unsupported language](https://servicenow-prod.fluidtopics.net/8pd1J9fmPPy9Yf9eLa8p4A "Translate the interface of an instance to a language for which ServiceNow does not provide an internationalization (I18N) plugin.").