---
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


---

# Cross-scope privileges for Localization Workspace

# Cross-scope privileges for Localization Workspace {#ariaid-title1}

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

After you create custom translation artifacts, set cross-scope privileges so that your artifacts can be accessed from Localization Workspace.

## Before you begin

* Ensure that your custom artifact has a processor script which includes a method named getTranslatableContent.
* Confirm the name of the table where your custom artifact's records are stored. Also confirm the table's application scope. You can find this information in the artifact's record in \[sn_lf_config\]. Detailed table information can also be found in \[sys_db_object\].
* Set your application scope to Localization Workspace.
* Role required: admin. The localization_admin can't complete this procedure.
{#lw-cross-scope-privilege__ul_gmd_qn4_bgc}

## About this task

Your custom artifacts are located in different application scopes, so you must provide access to them from the Localization Workspace application scope. Completing this configuration makes your artifacts visible and selectable in translation requests.  
For each artifact, set two entries in Cross scope privileges \[sys_scope_privilege\]:

1. A record for the artifact's table.
2. A record for the artifact's processor script.

{#lw-cross-scope-privilege__ol_ufv_fxj_1gc}The source scope for these records should be Localization Workspace.

Artifacts that are available by default don't need manual configuration of cross-scope privilege. For more information, see [Types of Localizable content in Localization Workspace](https://www.servicenow.com/docs/WJ4KXZ~KOnXxzZq74utz6Q "Localization Workspace collects available translatable content from across your instance when you create a translation request. You can make your content available by configuring permissions and creating an artifact record.").

## Procedure

1. Ensure that you are in the Localization Workspace application scope, and navigate to AllSystem ApplicationsApplication Cross-Scope Access.
2. On the Cross scope privileges \[sys_scope_privilege\] list, select New.  
   The Source Scope and Application fields are automatically set to Localization Workspace on the form.
3. On the form, fill in the fields to create a record for your artifact's table.  
   {#lw-cross-scope-privilege__table_evg_bq2_1gc__entry__2}

   | Field | Description |
   |-|-|
   | Target Scope | Enter the name of the application scope associated to your artifact table. |
   | Target Name | Enter the name of the table where your artifact is stored (such as \[kb_knowledge\]). |
   | Target Type | Select <kbd class="ph userinput">Table</kbd> from the list. |
   | Operation | Select <kbd class="ph userinput">Read</kbd>. |
   | Status | Select <kbd class="ph userinput">Allowed</kbd>. |
   [Table 1. Cross scope privilege: Table]

   {#lw-cross-scope-privilege__table_evg_bq2_1gc}
4. Select Submit to complete the record for the artifact's table.
5. Create another record for your artifact's Processor script by selecting New on Cross scope privileges \[sys_scope_privilege\].
6. On the form, fill in the fields to create a record for your artifact's processor script.  
   {#lw-cross-scope-privilege__table_gsh_my2_1gc__entry__2}

   | Field | Description |
   |-|-|
   | Target Scope | Enter the name of the application scope associated to your artifact. |
   | Target Name | Enter the name of the processor script. |
   | Target Type | Select <kbd class="ph userinput">Script Include</kbd>. |
   | Operation | Select <kbd class="ph userinput">Execute API</kbd>. |
   | Status | Select <kbd class="ph userinput">Allowed</kbd>. |
   [Table 2. Cross scope privilege: Processor script]

   {#lw-cross-scope-privilege__table_gsh_my2_1gc}
7. Select <kbd class="ph userinput">Submit</kbd> to complete the record for the artifact's Processor script.

## What to do next

You may also need to set Restricted Caller Access privileges to make restricted resources available to Localization Workspace. For more information 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.").
**Related tasks**   

* [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.")
* [Create a processor script](https://www.servicenow.com/docs/mmFfRnVM56_MWb3~0H2KWg "You can create a processor script to include in your custom artifact configuration to extract the translatable content and save the translated content.")  
**Related reference**   

* [Types of Localizable content in Localization Workspace](https://www.servicenow.com/docs/WJ4KXZ~KOnXxzZq74utz6Q "Localization Workspace collects available translatable content from across your instance when you create a translation request. You can make your content available by configuring permissions and creating an artifact record.")

*[\>]: and then