---
sourceDocument: Zurich ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/platform-administration

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Configuring Localization Workspace

# Configuring Localization Workspace {#ariaid-title1}

* Release version: Zurich
* 
* Updated December 11, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Configuring Localization Workspace

Localization Workspace enhances ServiceNow's AI Platform by providing comprehensive localization capabilities.
It requires configuring several prerequisite applications and dependencies before use.
From version 2.0.2, two Guided Setups simplify initial and prerequisite configurations.
Admins can subsequently manage settings via the Configuration Hub within Localization Workspace.
Show full answer Show less  

## Key Features

* **Prerequisites and Dependencies:** Install and configure related applications like Localization Framework and language plugins according to business language requirements.
* **Role Management:** Assign roles from Localization Framework along with the specific **snlw.user** role for all Localization Workspace users. Create groups and assign appropriate roles for user management.
* **Artifact Configuration:** Configure translation artifacts used within Localization Workspace. Assign the **sncd.contentadmin** role to users who need to manage Content Publishing artifacts or request their translation.
* **Settings Configuration:** Adjust workflow settings for translation tasks and enable project preferences such as enabling projects while disabling auto-creation of projects.
* **Translation Management Integration:** Configure any Translation Management System used by your organization and set up Dynamic Translation if utilizing machine translation services.
* **Custom Artifacts and Access Controls:** Create custom translation artifacts, set cross-scope privileges for artifact access, and configure Restricted Caller Access to enable Localization Workspace access to restricted resources when necessary.
* **Language Setup:** Manage target languages and translation providers flexibly, allowing end-users to select appropriate options when creating translation requests.
* **Configuration Hub:** Centralized interface for admins to manage dependent applications and properties without leaving Localization Workspace.
* **Email Notifications:** Admins can configure email alerts for Localization Workspace events to keep users informed.

## Key Outcomes

By following this configuration process, ServiceNow customers enable a streamlined and integrated localization workflow that supports multiple languages and translation providers. The setup ensures proper role-based access, artifact management, and seamless integration with translation services, providing an efficient environment to manage translation and localization tasks within ServiceNow. The Configuration Hub and Guided Setups reduce administrative overhead, while flexible language and artifact configurations support diverse business needs.  
Before using Localization Workspace, configure prerequisites, dependencies, and translation service providers.

## Configuration overview {#configuring-localization-workspace__cf-config-parent-checklist}

Localization Workspace builds upon the functionality of other ServiceNow AI Platform applications related to localization. These applications are activated with Localization Workspace if they are not already installed. You must complete the configuration of these applications before configuring Localization Workspace.  
Note:  
From version 2.0.2, the Localization Workspace interface provides two [Guided Setups](https://www.servicenow.com/docs/access?context=guided-setup&version=zurich&pubname=zurich-platform-user-interface&ft:locale=en-US) to lead admins through the process of configuration, as follows.

* With the admin role, navigate to Localization WorkspaceLocalization Framework Guided Setup for the prerequisite application.
* Next, navigate to Localization WorkspaceLocalization Workspace Guided Setup.

{#configuring-localization-workspace__ul_gbc_4hc_jhc}After the initial setup, admins can make adjustments to configurations by using the [Configuration Hub in Localization Workspace](https://www.servicenow.com/docs/l~phixSvFvWV_UsssAAs5g "Configuration Hub provides centralized access to the tables and properties often used by admins. You can update the tables and properties of dependent applications such as Localization Framework without leaving the Localization Workspace interface.").

1. [Install Localization Workspace](https://www.servicenow.com/docs/rSiavSfMvgOmeSHq5qvHlw "You can install the Localization Workspace application (sn_lw) if you have the admin role. The application installs related ServiceNow Store applications and plugins if they are not already installed. Demo data isn't available.").

   You can install the application (sn_lw) if you have the admin role. The application installs related applications and plugins if they are not already installed. Check your
   entitlements to determine whether you have access to Localization Workspace.
2. Configure prerequisites as needed.In the Zurich release, access to the Settings table \[sn_lf_setting\] is configured by default. However, in the Yokohama release, you must confirm access to the Settings table \[sn_lf_setting\]. The admin role is required for this step. See [Confirm access to Settings table](https://www.servicenow.com/docs/VToEgb_onv5~DuIqJAaf2w "As part of the configuration for Localization Workspace, confirm access to the Settings table of Localization Framework.").

3. Configure dependencies.
   * [Internationalization (i18n) and language plugins](https://www.servicenow.com/docs/hQV3b9dqIxH71KtsBTG2lw "Learn about support for localizing ServiceNow instances as part of your globalization strategy."): Install language plugins as part of System Localization. Choose your instance's languages according to your business requirements.
   * [Localization Framework:](https://www.servicenow.com/docs/8A4FFAffEwv66A61oEhS9A "Learn more about the Localization Framework app that enables a systematic localization process, so you can provide a seamless user experience in multiple languages.") Configure Localization Framework as follows.  
     Assign roles. Localization Workspace uses roles from Localization Framework, along with one role specific to Localization Workspace.
     1. Add Localization Framework roles as needed. See [Localization Framework Roles](https://www.servicenow.com/docs/cBr8qxvOafMO~JiIMTrPhA#roles-localization-framework "Localization Framework uses different roles to manage different aspects of the application. The roles from Localization Framework are also used in Localization Workspace.").
     2. Add the Localization Workspace user role sn_lw.user. This role is required for all users in Localization Workspace.
     {#configuring-localization-workspace__ol_mvr_24x_jfc}Create at least one group in the Groups \[sys_user_group\] table and add roles to the group, then assign your localization users to the appropriate group.  
     Configure artifacts. See [Artifact configurations](https://www.servicenow.com/docs/HmhILma7TH_65Ft459B~AQ "You can configure the required artifacts and use the Localization Framework to fulfill the translation requests.").  
     Note:  
     The role sn_cd.content_admin is required to see Content Publishing artifacts from Localization Workspace. If your users need the ability to request translations of Content Publishing artifacts, add sn_cd.content_admin to the appropriate group.  
     Configure settings, including for the workflows of translation tasks. See [Localization Framework settings](https://www.servicenow.com/docs/p~g8etNiz~Jrrvksj2rXzg "You can define translation and workflow preferences for one or more languages and for one or all the available artifacts with Localization Framework settings."). Also on the Localization Framework settings table (sn_lf_settings), in the Project Preferences tab, ensure that check boxes are set as follows.
     * Enable projects: Selected.
     * Enable auto creation: Cleared (unselected).
     {#configuring-localization-workspace__ul_cfg_xdy_vfc}

     Configure a Translation Management System if your organization uses one. See [Translation Management System configurations](https://www.servicenow.com/docs/5TvYUeFzD_Pn4hRVwvuKgQ "The Localization Framework supports integration with a translation management system to localize the content.").
   * [Dynamic Translation](https://www.servicenow.com/docs/oSQhkE4LK5zPEpCdUEOoYQ "With Dynamic Translation you can support machine translation from one language to another across your instance."): If you use machine translation to fulfill translation requests, configure Dynamic Translation, including setting up a translator configuration. See [Integration with other translation services](https://www.servicenow.com/docs/54Mz_hsSJEnD_nVptK~9tg "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.").
4. Configure custom artifacts, if you plan to use your own artifacts in Localization Workspace. See [Create and configure a custom artifact](https://www.servicenow.com/docs/5oBC4OcXJsESwVE8YlmIWA "Create and configure custom artifacts of your choice to use the Localization Framework functionality.").

   Set cross-scope access privileges for your artifacts. For more information see [Cross-scope privileges for Localization Workspace](https://www.servicenow.com/docs/tcLGnyllcnEKJGmhp1YfuA "After you create custom translation artifacts, set cross-scope privileges so that your artifacts can be accessed from Localization Workspace.").

   Set Restricted Caller Access for Localization Workspace to enable access to artifact resources, if needed. The admin role is required for this step. See [Restricted Caller Access for Localization Workspace](https://www.servicenow.com/docs/osk5P0lLPSKuKN6HRPbgrQ "Give Localization Workspace access to your content by setting Restricted Caller Access privileges. Setting these privileges is required only when target tables or scripts are restricted.").
5. [Configure languages](https://www.servicenow.com/docs/MKCa8ma53NWZ8TbUgJMV1Q "Language setup enables you to flexibly configure target languages and their third-party translation service providers. When your users create translation requests, they can select the languages and providers you have configured.") in Localization Workspace. Language providers in Localization Workspace are different from translator configurations in Dynamic Translation.

{#configuring-localization-workspace__ol_y1d_nbw_bfc}
* **[Install Localization Workspace](https://www.servicenow.com/docs/rSiavSfMvgOmeSHq5qvHlw)**   
  You can install the Localization Workspace application (sn_lw) if you have the admin role. The application installs related ServiceNow® Store applications and plugins if they are not already installed. Demo data isn't available.
* **[Confirm access to Settings table](https://www.servicenow.com/docs/VToEgb_onv5~DuIqJAaf2w)**   
  As part of the configuration for Localization Workspace, confirm access to the Settings table of Localization Framework.
* **[Cross-scope privileges for Localization Workspace](https://www.servicenow.com/docs/tcLGnyllcnEKJGmhp1YfuA)**   
  After you create custom translation artifacts, set cross-scope privileges so that your artifacts can be accessed from Localization Workspace.
* **[Restricted Caller Access for Localization Workspace](https://www.servicenow.com/docs/osk5P0lLPSKuKN6HRPbgrQ)**   
  Give Localization Workspace access to your content by setting Restricted Caller Access privileges. Setting these privileges is required only when target tables or scripts are restricted.
* **[Configuration Hub in Localization Workspace](https://www.servicenow.com/docs/l~phixSvFvWV_UsssAAs5g)**   
  Configuration Hub provides centralized access to the tables and properties often used by admins. You can update the tables and properties of dependent applications such as Localization Framework without leaving the Localization Workspace interface.
* **[Language setup in Localization Workspace](https://www.servicenow.com/docs/MKCa8ma53NWZ8TbUgJMV1Q)**   
  Language setup enables you to flexibly configure target languages and their third-party translation service providers. When your users create translation requests, they can select the languages and providers you have configured.
* **[Creating email notifications for Localization Workspace](https://www.servicenow.com/docs/1SHzqD3dlVCg~QAVNZSDgw)**   
  As an admin, you can set up email notifications for events in Localization Workspace.

*[\>]: and then


