---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/platform-administration

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Localization Framework Roles

# Localization Framework Roles {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Localization Framework uses different roles to manage different aspects of the application. The roles from Localization Framework are also used in Localization Workspace.
For more information about Localization Workspace, see [Localization Workspace](https://servicenow-prod.fluidtopics.net/dHGng1GgKEqZWAY~mdZesw "Localization Workspace is a targeted translation management experience for content owners and translation requesters. With Localization Workspace you can manage and deliver multilingual content at scale."). To learn more about managing subscriptions, see [Managing per-user subscriptions in Subscription Management](https://servicenow-prod.fluidtopics.net/ElhgAhTYv8j45~LzI~mvAg "Manage your per-user subscription allocations using Subscription Management.") and contact your account representative.

## Localization administrator \[localization_admin\] {#ariaid-title2}

Manage the following aspects of the Localization Framework application. This role is also used in Localization Workspace.
* Configures the supported artifacts and custom artifacts for Localization Framework.
* Configures localization settings for the activated languages.
* Can request translations into multiple languages for Service Catalog items, Virtual Agent topics, or for any custom artifacts from their respective artifact tables.
* Can request translations for Service Catalog items, Virtual Agent topics, or for any custom artifact for a particular language from their respective artifact reports in the insights dashboard.
* Can configure RWS and XTM TMS and can create and configure a custom TMS by inheriting the following roles:
  * flow_designer: Can edit the TMS subflows and can create a new TMS configuration record.
  * connection_admin: Can access the connections and credentials tables and records.
  {#local-framework-role-1__ul_mnn_pnk_xnb}
* Owns the localization insights dashboard and reports. Can execute the scheduled jobs to display the reports on the dashboard.
* Views the localization health of the system.
* Inherits the localization_editor, localization_fulfiller, localization_manager, and localization_requestor roles.
{#local-framework-role-1__ul_slt_d32_wnb}

### Contains Roles {#local-framework-role-1__section-feature-role-contains-roles}

List of roles contained within the role.  
* localization_editor
* localization_fulfiller
* localization_manager
* localization_requestor
{#local-framework-role-1__ul_urj_rt5_g1c}

### Groups {#local-framework-role-1__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#local-framework-role-1__section-feature-role-considerations}

Note:  
Avoid granting an admin role when more specialized roles are available.
When working in Localization Workspace, the role sn_cd.content_admin is required to see Content Publishing artifacts.

## Localization requester \[localization_requestor\] {#ariaid-title3}

Request translations for all the configured artifacts into one or more languages. This role is used in Localization Framework and Localization Workspace.

### Contains Roles {#local-framework-role-2__section-feature-role-contains-roles}

List of roles contained within the role.

None.

### Groups {#local-framework-role-2__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#local-framework-role-2__section-feature-role-considerations}

Note:  
Localization requester can fulfill translations by inheriting the localization_fulfiller role.
When working in Localization Workspace, the role sn_cd.content_admin is required to see Content Publishing artifacts.

## Localization fulfiller \[localization_fulfiller\] {#ariaid-title4}

Provide translations for the requested artifact items and approve and publish the translations. This role is used in Localization Framework and Localization Workspace.

### Contains Roles {#local-framework-role-3__section-feature-role-contains-roles}

List of roles contained within the role.

None.

### Groups {#local-framework-role-3__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#local-framework-role-3__section-feature-role-considerations}

Fulfillers can translate a localization task in the following ways:

* Manually translate in the Localization Task web page.
* Use machine translation by submitting the item to a third-party translator configured in Dynamic Translation.
* Export source files to a third-party translator and import the returned translations.
* Send the source files for translation via email and receive the translated files via email.
* Send translatable items to a translation management system (TMS).
* Verify and approve the translations.
* Publish the translations if the language workflow has no approval flow.
{#local-framework-role-3__ul_s5t_yv2_tnb}

## Localization editor \[localization_editor\] {#ariaid-title5}

Localization editors can translate content without the need for a localization task. This role is used in Localization Framework and Localization Workspace.

### Contains Roles {#local-framework-role-4__section-feature-role-contains-roles}

The Localization editor role contains the Localization Requester \[localization_requestor\] role.

### Groups {#local-framework-role-4__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#local-framework-role-4__section-feature-role-considerations}

Users assigned to this role can translate content from Virtual Agent Designer
NLU Workbench, and Document Templates of HR Service Delivery.

A localization editor can translate the content using machine translation, and also by exporting and importing the content.

## Localization manager \[localization_manager\] {#ariaid-title6}

Owns the localization projects and adds the localization requested items to the projects. Only a Localization manager has the authority to start the project. This role is used by Localization Framework and Localization Workspace.

### Contains Roles {#local-framework-role-5__section-feature-role-contains-roles}

The Localization manager role contains the Localization fulfiller \[localization_fulfiller\] role.

### Groups {#local-framework-role-5__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#local-framework-role-5__section-feature-role-considerations}

If the Localization Framework Hub and Spoke architecture is activated, the localization_manager role has access to the following tables on the hub instance:

* Localization Framework Hub Translation Request \[sn_lf_hub_translation_request\]
* Localization Framework Hub Translation Item \[sn_lf_hub_translation_item\]

{#local-framework-role-5__ul_dc5_hx5_g1c}For more information, see [Localization Framework Hub and Spoke architecture](https://servicenow-prod.fluidtopics.net/tmVS34WjiPOa552hsX8exg "Enable one central instance to fulfill translation requests submitted from other instances using the Localization Framework Hub and Spoke architecture. Install optional Localization Framework plugins to configure one of your instances as a hub and other instances as spokes.").