---
sourceDocument: Australia ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/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 Workspace Roles

# Localization Workspace Roles {#ariaid-title1}

* Release version: Australia
* 
* Updated June 3, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Localization Workspace is installed with these roles.

## Localization Framework roles used in Localization Workspace {#localization-workspace-roles__section_lfx_rfs_hjc}

Many roles used in Localization Workspace are inherited from Localization Framework. For detailed information about the following, see [Localization Framework Roles](https://www.servicenow.com/docs/T0tK7jauLR7fBvBgIrzboA#roles-localization-framework "Localization Framework uses different roles to manage different aspects of the application. The roles from Localization Framework are also used in Localization Workspace.").{#localization-workspace-roles__table_cm4_hhs_hjc__entry__2}

| User | Name |
|-|-|
| Localization administrator | localization_admin |
| Localization editor | localization_editor |
| Localization fulfiller | localization_fulfiller |
| Localization manager | localization_manager |
| Localization requester | localization_requestor |
[Table 1. Roles from Localization Framework]

{#localization-workspace-roles__table_cm4_hhs_hjc}

## Terminology Manager (sn_lw.terminology_manager) {#ariaid-title2}

Upload, review, and manage glossaries in the Language Asset Management area of Localization Workspace.

### Contains Roles {#localization-workspace-role-1__section-feature-role-contains-roles}

List of roles contained within the role.  
* import_transformer
* content_admin
* import_set_loader
{#localization-workspace-role-1__ul_csj_pl1_3jc}

### Groups {#localization-workspace-role-1__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#localization-workspace-role-1__section-feature-role-considerations}

The sn_lw.terminology_manager role is available from version 3.1.0 of Localization Workspace. With version 3.1.0, the following roles that had previously been contained in sn_lw.user are transferred to sn_lw.terminology_manager: import_transformer, content_admin,
import_set_loader.

This role does not contain the sn_lw.user role. Be sure to also assign sn_lw.user to any user working in Localization Workspace.

## Localization Workspace user (sn_lw.user) {#ariaid-title3}

Assign this role to any user working in Localization Workspace.

### Contains Roles {#localization-workspace-role-2__section-feature-role-contains-roles}

List of roles contained within the role, before version 3.1.0.  
* import_transformer
* content_admin (from version 3.0.0)
* import_set_loader
* canvas_user (from version 2.0.0)
{#localization-workspace-role-2__ul_ghr_4n1_3jc}

From version 3.1.0, the roles contained within this role:

canvas_user

### Groups {#localization-workspace-role-2__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#localization-workspace-role-2__section-feature-role-considerations}

Note:  
From version 3.1.0, the following contained roles are transferred from sn_lw.user to sn_lw.terminology_manager: import_transformer, content_admin, import_set_loader.

The sn_cd.content_admin role is required to see Content Publishing items from Localization Workspace. The sn_cd.content_admin role is different from the content_admin role.
For more information about
sn_cd.content_admin, see [Types of Localizable content in Localization Workspace](https://www.servicenow.com/docs/7k0_Gw_ZHiW_14Ai7ZP4QQ "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.").

