---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Configure the Localization Framework preferences

# Configure the Localization Framework preferences {#ariaid-title1}

* Release version: Xanadu
* 
* Updated July 28, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

Configure the preferences to request the translation in the activated
languages.

## Before you begin

Role required: localization_admin or localization_manager

## Procedure

1. Navigate to AllLocalization FrameworkSettings.
2. Select New.
3. On the form, fill in the fields.  
   {#define-translation-preferences__table_hqt_4lv_pnb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Identifier of the translation setting. |
   | Artifact | Artifact for the settings being defined. You can select either All Artifacts or an artifact of your choice, such as catalog_item or nlu_model. Note: To select Virtual Agent topics, Document Templates, Document Template Block Content, HTML Document Template, Knowledge Base or Email notification artifacts, you must activate specific plugins. For more information, see [Supported artifacts in Localization Framework](https://www.servicenow.com/docs/MRlLvn70GhrLaenULw~EXg "Localization Framework extends its framework capabilities to certain artifacts and translates the content of the artifact items."). |
   | Languages | Target records of the languages available in the instance. All the available languages are populated based on the artifact selected. |
   [Table 1. Settings form]

   {#define-translation-preferences__table_hqt_4lv_pnb}
4. Select the Translation Preferences tab.
5. On the form, fill in the fields.  
   {#define-translation-preferences__table_nyc_xct_shb__entry__2}

   | Field | Description |
   |-|-|
   | Machine Translation ||
   | Enable machine translate | Option to enable the machine translation service for selected languages. Note: Dynamic Translation must be installed to use machine translation. For more information, see [Activate Dynamic Translation](https://www.servicenow.com/docs/KlFs316vpp~CtKtT~jcivA "Activate the Dynamic Translation plugin (com.glide.dynamic_translation) to enable all the required APIs."). |
   | Translator | List of the available translator services for machine translation. Note: Ensure that at least one third-party translator configuration record is integrated and active. For more information, see [Integration with other translation services](https://www.servicenow.com/docs/U1fSr7~Pm5whrtpaSeoRKA "Enable machine translation on your instance by integrating third-party translator services with Dynamic Translation. You can configure one or more translation service providers of your choice."). |
   | Translation Management System ||
   | Enable TMS | Option to enable Translation Management System (TMS) for selected languages. |
   | TMS | List of all the TMS services available for machine translation. By default, the RWS and the XTM TMS are available. You can also choose a configured custom TMS. For more information, see [Translation Management System configurations](https://www.servicenow.com/docs/aSMY6dId38Fo0cuJRYFQUA "The Localization Framework supports integration with a translation management system to localize the content."). If you are configuring a spoke instance per the Localization Framework Hub and Spoke architecture, select <kbd class="ph userinput">Localization Framework Hub</kbd> in this field. For more information, see [Localization Framework Hub and Spoke architecture](https://www.servicenow.com/docs/cflazf3Fkr9maXwPPM8yFA "Enable one central instance to fulfill translation requests submitted from other instances using the Localization Framework Hub and Spoke architecture. Install optional Localization Framework plugins to configure one of your instances as a hub and other instances as spokes.") . |
   | Send via Email ||
   | Enable send via email | Option to enable email service for content localization for selected languages. |
   | Email subflow | Available subflows for your email. Automatically, a subflow exists. To choose another subflow, create a subflow before setting up the translation preference. |
   | Default file format | Option to select a file format to send and receive the content. By default, XLIFF 1.2 and CSV file formats are supported. |
   | Default recipient(s) list | List of recipient email addresses through which the content is sent to the translator for translation. |
   | Export/Import ||
   | Enable export/import | Option to enable the export and import of content for the translation of selected languages. |
   | Default file format | Available options of file formats to send and receive the content. By default, XLIFF 1.2 and CSV file formats are supported. |
   [Table 2. Translation Preferences form]

   {#define-translation-preferences__table_nyc_xct_shb}
6. Select the Workflow Preferences tab.
7. On the form, fill in the fields.  
   {#define-translation-preferences__table_lt1_x3d_qnb__entry__2}

   | Field | Description |
   |-|-|
   | Workflow | List of all the workflows available for the translation process. For more information on the available workflows, see [Workflows in the Localization Framework](https://www.servicenow.com/docs/y7LHLQSLWNKiw55CqnKe3g "Workflows define actions for completing a localization task. Each localization task undergoes the workflow configured for its target language to complete the task."). |
   | Business approver group | List of all the available business approver groups. This field appears only when a workflow that requires business approvals is selected from the Workflow field. Note: Ensure that the business approver group contains the localization_fulfiller role. |
   | Localization fulfiller group | List of all the available localization fulfiller groups. Note: Ensure that the localization fulfiller group contains the localization_fulfiller role. |
   | Auto translation mode | Option to select the auto-translation mode. The available options are as follows: * Machine Translate * Send to TMS. If the instance has been set up as a spoke in the[Localization Framework Hub and Spoke architecture](https://www.servicenow.com/docs/cflazf3Fkr9maXwPPM8yFA "Enable one central instance to fulfill translation requests submitted from other instances using the Localization Framework Hub and Spoke architecture. Install optional Localization Framework plugins to configure one of your instances as a hub and other instances as spokes."), this setting will submit the translation request to the hub. * Send via Email {#define-translation-preferences__ul_pzn_khx_gsb}For more information, see [Translation Modes](https://www.servicenow.com/docs/I529UKxmur6bok64V4c5iQ "The Localization Framework offers various translation modes for content translation. Localization fulfillers can use one of the translation modes to translate content and fulfill localization requests.") Note: Ensure that you have configured the Translation Preferences for the selected auto translation mode. |
   | Translation approver group | List of all the available translation approver groups. This field appears only when a workflow that requires translation approvals is selected from the Workflow field. Note: Ensure that the translation approver group contains the localization_fulfiller role. |
   [Table 3. Workflow Preferences form]

   {#define-translation-preferences__table_lt1_x3d_qnb}
8. Select the Project Preferences tab.
9. On the form, fill in the fields.  
   {#define-translation-preferences__table_f3x_d5z_ztb__entry__2}

   | Field | Description |
   |-|-|
   | Enable projects | Option to enable the creation of the localization projects. If this option is enabled if the translation of the artifact is requested, the localization requested items (LRITMs) are created. You can then create a project and add the corresponding requested items to start the translation. You must have localization_manager role to create a project. This option helps in the bulk translation of the artifacts to be done at the same time by adding them to a project. Then, the translation progress of the LRITMs is monitored at the project level. |
   | Enable auto creation | Option to enable the auto creation of the localization projects. If this option is enabled if the translation of the artifact items is requested, then the following occur: * A localization project is auto created. The corresponding localization requested items (LRITMs) are created, bundled, and added to the localization project. * The project starts automatically based on the localization framework settings. {#define-translation-preferences__ul_r4r_hvz_ztb} |
   | Localization manager group | List of all the available user groups. Note: Ensure that the localization manager group contains the localization_manager role. |
   [Table 4. Project Preferences form]

   {#define-translation-preferences__table_f3x_d5z_ztb}
10. Select Submit.

*[\>]: and then