---
title: Dynamic artifact detection in Localization Workspace
description: With Dynamic artifact detection, Localization Workspace identifies all translatable content, including your custom artifacts.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-administration/localization-workspace/lw-dynamic-artifact-detection.html
release: australia
product: Localization Workspace
classification: localization-workspace
topic_type: concept
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Exploring Localization Workspace, Localization Workspace, Translation and localization, Configure core features, Administer the ServiceNow AI Platform]
---

# Dynamic artifact detection in Localization Workspace

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-request-translations-types.md) 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-framework/create-configure-custom-artifact.md).
-   You must set Cross-scope privileges for your artifact's table and processor script. For information, see [Cross-scope privileges for Localization Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-cross-scope-privilege.md).
-   You may also need to set Restricted Caller Access for artifact resources. For information, see [Restricted Caller Access for Localization Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-restricted-caller-access.md).

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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-localizable-content.md).

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