--- title: Upload glossaries to Language Asset Management description: Upload glossaries to the Language Asset Management area of Localization Workspace. Create a glossary by entering source terms and translations in the provided spreadsheet template, then uploading the completed spreadsheet to Language Asset Management. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/platform-administration/localization-workspace/lw-lam-upload-glossaries.html release: australia product: Localization Workspace classification: localization-workspace topic_type: task last_updated: "2026-05-28" reading_time_minutes: 5 breadcrumb: [Language Asset Management, Configuring Localization Workspace, Localization Workspace, Translation and localization, Configure core features, Administer the ServiceNow AI Platform] --- # Upload glossaries to Language Asset Management Upload glossaries to the Language Asset Management area of Localization Workspace. Create a glossary by entering source terms and translations in the provided spreadsheet template, then uploading the completed spreadsheet to Language Asset Management. ## Before you begin - Confirm that the Languages \[sys\_language\] table in your instance contains an ID for every language that you plan to include in your glossary. Language IDs should be compliant with BCP 47. For more information and links see [Language Asset Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-language-asset-management.md). - You must be able to work with and save files in the Excel Workbook \(.xlsx\) file format. This file format supports the UTF-8 encoding that is needed for special characters and non-alphabetic writing systems. - Role required: sn\_lw.user. From version 3.1.0, both the sn\_lw.user and the sn\_lw.terminology\_manager roles are required. ## About this task From version 3.0.0, the Language Asset Management area of Localization Workspace enables you to upload glossaries for editing and storage. - Glossaries consist of source terms and their translations. Each source term can have translations into one or more languages. - After you initially create a glossary by uploading a spreadsheet, you can make updates or add new terms in the product UI. See [Edit a glossary in Language Asset Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/localization-workspace/lw-lam-edit-glossary.md). - The same source term can be listed in multiple glossaries. A source term repeated in two different glossaries is considered to be two different records, with different translations possible. Similarly, a source term can be repeated in one glossary if assigned to different categories within that glossary \(Product/Service or Part of Speech\). Repeated source terms are considered to be two different records, with different translations possible. The following procedure involves downloading an Excel Workbook \(.xlsx\) spreadsheet template, filling it out, and uploading the completed file to your instance. Some of the columns have drop-down selections, as noted in the table in the procedure. For these columns, you must choose a value from the drop-down selection. ## Procedure 1. Navigate to **All** > **Localization Workspace** > **Language Asset Management**. 2. Select **Import Glossary**. \[Omitted image "lw-lam-import-glossary-button-a.png"\] Alt text: In the Language Asset Management area, the Import Glossary button is highlighted. **Note:** If you have a completed spreadsheet ready to upload, skip to the next **Import glossary** step in this procedure. 3. In the **Import glossary** modal window, select the **ServiceNow\_Glossary\_template.xlsx** attachment and download it. \[Omitted image "lw-lam-upload-glossaries-dl-template-a.png"\] Alt text: On the modal window titled Import glossary, the template download area is highlighted. The template filename is ServiceNow\_Glossary\_Template.xlsx 4. Using one row for a source term and its translations, and using drop-down selections where applicable, fill in the spreadsheet according to the following guidance.
| Column | Value |
|---|---|
| **glossary\_name** | This is displayed as **Glossary Name** in the UI. Each row should have a value in the glossary\_name column. |
| **glossary\_description** | \(Optional\). Enter a description of the glossary. This value is displayed as **Glossary Description** in the UI. |
| **product\_service** | This is displayed as **Product/Service** in the UI, and is a way to filter or subdivide a glossary. Use this if a source term has different translations depending on the Product/Service. **Note:** The same source term can be listed multiple times in one glossary when associated to different product\_service values. |
| **term** | Enter the source term \(the original word or phrase\). Terms can contain spaces, special characters, and punctuation marks. Source terms can be written in languages other than English. However, translation requests in Localization Workspace must be from English to non-English languages. You can enter the same source term multiple times, but each variation must be assigned to either a different Part of Speech or a different Product/Service category. |
| **definition** | The definition for the source term. |
| **part\_of\_speech** | This is a drop-down selection in the template. Choose from noun, verb, and so forth.**Note:** The same source term can be listed multiple times in one glossary when associated to different part\_of\_speech values. |
| **do\_not\_translate** | This is a boolean drop-down selection in the template. Choose TRUE when terms shouldn't be translated. |
| **source\_language** | This is a drop-down selection in the template. Choose the language ID of the source term. |
| **\(language ID codes\)** | Enter the translations in the same row as the source term. The template contains columns for each language supported in the platform. The column headers are BCP 47 language ID codes.- You can enter non-alphabetic terms and special characters. - You can leave values blank. - Clear the cell contents for any values you don't want applied to your glossary. This includes placeholder values such as "Translation1". You can add you own columns for self-localized languages. If you create a column, use only language ID codes that exist in your sys\_language table as the column headers. |