--- sourceDocument: Brazil ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Configuring Localization Workspace # Configuring Localization Workspace {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 is a ServiceNow application designed to streamline and manage localization and translation tasks. Before using Localization Workspace, administrators must configure prerequisites, dependencies, and translation service providers. The application builds on other ServiceNow AI Platform localization tools, which are installed and configured first if not already present. Show full answer Show less From version 2.0.2 onwards, Localization Workspace offers two guided setup processes to assist admins in configuring the Localization Framework and Localization Workspace itself. After initial setup, admins can manage configurations centrally through the Configuration Hub. ## Key Configuration Steps * **Installation:** Admins with the admin role can install Localization Workspace (snlw), which automatically installs required related applications and plugins. * **Access and Permissions:** Confirm access to the Localization Framework Settings table \[snlfsetting\], especially for instances running Yokohama release or later. Assign necessary roles such as snlw.user for Localization Workspace users, snlw.terminology for terminology management, and sncd.contentadmin for Content Publishing translation requests. * **Dependencies:** Install and configure Internationalization (i18n) and language plugins based on your organizational language requirements. Configure Localization Framework roles and groups, assigning users appropriately for localization tasks. * **Artifact and Workflow Configuration:** Set up translation artifacts and workflows. Configure Localization Framework settings, including enabling projects and managing project preferences. * **Translation Management System and Dynamic Translation:** Integrate your Translation Management System if used, and configure Dynamic Translation for machine translation workflows including translator configurations. * **Custom Artifacts and Privileges:** If using custom translation artifacts, configure cross-scope access privileges and Restricted Caller Access to ensure Localization Workspace can access necessary resources. * **Language Setup:** Configure target languages and third-party language providers within Localization Workspace. Guided tours are available from version 3.0.0 to assist with language provider and group configuration. * **Glossaries and AI Support:** Optionally upload and manage glossaries via Language Asset Management. From version 4.0, AI-generated glossaries can be enabled through the Generate Glossary skill. * **Email Notifications:** Admins can set up email notifications for various Localization Workspace events to keep stakeholders informed. ## Key Outcomes * Streamlined localization management through a centralized interface and guided setup processes. * Proper role and permission assignments to ensure secure and efficient localization workflows. * Integration with machine translation and translation management systems to automate and optimize translation tasks. * Flexible language and provider configuration to meet diverse localization requirements. * Ability to manage glossaries and terminology effectively, enhancing translation consistency and quality. * Centralized configuration and monitoring through the Configuration Hub, reducing administrative overhead. Before using Localization Workspace, configure prerequisites, dependencies, and translation service providers. ## Configuration overview {#configuring-localization-workspace__cf-config-parent-checklist} Localization Workspace builds on 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=brazil&pubname=brazil-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/FB~iGWlzZDMn_Ph937eFAg "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/CxJVqhu5Q4jfgkiYDw3A4w "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.From 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/O45fvpFcYhkPmavy4R9A_A "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/xvlrvcLeDicxzOqqYZ6IPA "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/QQuCBCAYZiaTHUldU1MVxw "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 roles specific to Localization Workspace. 1. Add Localization Framework roles as needed. See [Localization Framework Roles](https://www.servicenow.com/docs/yYq2SD9Tqm4t_795rVGCeQ#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. 3. Add the Terminology Manager (sn_lw.terminology) role for working with glossaries in [Language Asset Management](https://www.servicenow.com/docs/Mrm0hydOWeuBdZHYQyGM0Q "Enhance localization in your instance with Language Asset Management in Localization Workspace. You can upload glossaries to Language Asset Management for editing and storage."). {#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/anKn7vQWjMLdTxdXwf9KmA "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 items from Localization Workspace. If your users need to request translations for Content Publishing material, add sn_cd.content_admin to the appropriate group. The sn_cd.content_admin role is different from the content_admin role. From version 3.0.0, the sn_lw.user role contains the content_admin role. Configure settings, including for the workflows of translation tasks. See [Localization Framework settings](https://www.servicenow.com/docs/wtzTJHwxcgbo_zsqiXyjyw "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/6j2L2qCW9OsoXO0kpVgr2w "The Localization Framework supports integration with a translation management system to localize the content."). * [Dynamic Translation](https://www.servicenow.com/docs/AALWOHCoik1bXqJt7gOWgg "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/__Ea6cYEr~MbF5e_XL7h2w "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/DVRLErcPaCI6j3PAn71~gg "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/z_H3eeM4tn0ApQBeulhhFQ "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/AX7RJF52~oGaqEbvXDMCXQ "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/gOg2M6EOOtIvKY4FIW6g3w "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. Note: From version 3.0.0, two guided tours are available. One guided tour assists with configuring a language provider, accessible to users with the Localization administrator role (localization_admin). The other guided tour assists with configuring language groups, and is accessible to the Localization administrator role and the Localization requester role (localization_requestor). Find the guided tours by selecting the Help Center icon ![]() on the Localization Workspace Home screen. 6. Optionally provide glossaries in [Language Asset Management](https://www.servicenow.com/docs/Mrm0hydOWeuBdZHYQyGM0Q "Enhance localization in your instance with Language Asset Management in Localization Workspace. You can upload glossaries to Language Asset Management for editing and storage."). 7. Optionally activate the Generate Glossary skill if you intend to generate glossaries using AI. From version 4.0. See [Globalization Terminology Agent](https://www.servicenow.com/docs/~U5TeqZIBvaR85tNk0C7JA "Generate a glossary of terms based on your English-language Knowledge Base articles. Use the glossary of terms to enhance language governance, quality, and consistency across the platform. Available from version 4.0 of Localization Workspace."). {#configuring-localization-workspace__ol_y1d_nbw_bfc} * **[Install Localization Workspace](https://www.servicenow.com/docs/CxJVqhu5Q4jfgkiYDw3A4w)** 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/O45fvpFcYhkPmavy4R9A_A)** 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/z_H3eeM4tn0ApQBeulhhFQ)** 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/AX7RJF52~oGaqEbvXDMCXQ)** 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/FB~iGWlzZDMn_Ph937eFAg)** 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 Asset Management](https://www.servicenow.com/docs/Mrm0hydOWeuBdZHYQyGM0Q)** Enhance localization in your instance with Language Asset Management in Localization Workspace. You can upload glossaries to Language Asset Management for editing and storage. * **[Language setup in Localization Workspace](https://www.servicenow.com/docs/gOg2M6EOOtIvKY4FIW6g3w)** 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/EeVMB0~~903IzmILm32alw)** As an admin, you can set up email notifications for events in Localization Workspace. *[\>]: and then