Configuring Localization Workspace
Before using Localization Workspace, configure prerequisites, dependencies, and translation service providers.
Configuration overview
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.
- With the admin role, navigate to for the prerequisite application.
- Next, navigate to .
- Install Localization Workspace.
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.
- 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.
- Configure dependencies.
- Internationalization (i18n) and language plugins: Install language plugins as part of System Localization. Choose your instance's languages according to your business requirements.
- Localization Framework: Configure Localization Framework as follows. Assign roles. Localization Workspace uses roles from Localization Framework, along with one role specific to Localization Workspace.
- Add Localization Framework roles as needed. See Localization Framework Roles.
- Add the Localization Workspace user role sn_lw.user. This role is required for all users in Localization Workspace.
Configure artifacts. See Artifact configurations.注: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. 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).
Configure a Translation Management System if your organization uses one. See Translation Management System configurations.
- Dynamic Translation: If you use machine translation to fulfill translation requests, configure Dynamic Translation, including setting up a translator configuration. See Integration with other translation services.
- Configure custom artifacts, if you plan to use your own artifacts in Localization Workspace. See Create and configure a custom artifact.
Set cross-scope access privileges for your artifacts. For more information see Cross-scope privileges for 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.
- Configure languages in Localization Workspace. Language providers in Localization Workspace are different from translator configurations in Dynamic Translation.注: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.