Cross-scope privileges for Localization Workspace

  • Release version: Australia
  • Updated March 12, 2026
  • 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.

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

    Procedure

    1. Ensure that you are in the Localization Workspace application scope, and navigate to All > System Applications > Application 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.
      Table 1. Cross scope privilege: Table
      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 Table from the list.
      Operation Select Read.
      Status Select Allowed.
    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.
      Table 2. Cross scope privilege: Processor script
      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 Script Include.
      Operation Select Execute API.
      Status Select Allowed.
    7. Select Submit 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.