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


---

# Dynamic artifact detection in Localization Workspace

# Dynamic artifact detection in Localization Workspace {#ariaid-title1}

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

With Dynamic artifact detection, Localization Workspace identifies all translatable content, including your custom artifacts.

When you create translation requests, your custom artifacts can be selected in the [content type](https://www.servicenow.com/docs/o0aRV4Vp~0ZS3zyLv0pM1A "Add content types to a translation request in Localization Workspace. Your translation request can include multiple types of documents from tables across your instance.") stage. All untranslated or partially translated documents in the artifact's table are retrieved and displayed to you.

To make custom artifacts (content types) available for selection, you must configure them as follows.

* Create your translation artifact in the Artifact Configurations \[sn_lf_config\] table. For details 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.").
* You must set Cross-scope privileges for your artifact's table and processor script. For 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.").
* You may also need to set Restricted Caller Access for artifact resources. For 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.").

{#lw-dynamic-artifact-detection__ul_qsg_wz4_bgc}

Some preconfigured artifact types are already available when you install Localization Workspace. For information about translation artifacts that are available by default, 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.").

For examples of Localization Framework artifacts that you can set up, see the LF Artifact blog posts list on <https://www.servicenow.com/community/international-localization/need-to-translate-a-par-dashboard-check-this/ta-p/2839751> in the ServiceNow Community. These examples include Processor scripts.