--- 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 --- # Language Asset Management # Language Asset Management {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Language Asset Management Language Asset Management in Localization Workspace enhances instance localization by enabling you to upload, store, and edit glossaries. Glossaries are lists of source terms with translations into multiple languages, facilitating consistent and context-sensitive translations across your organization. Show full answer Show less ## Key Features * **Glossary Management:** Create multiple glossaries organized by business unit, function, or locale. Each glossary can be subdivided or filtered by Product/Service category. * **Contextual Translation:** Source terms can appear under different categories, allowing distinct translations depending on context. * **Multilingual Support:** Provide translations for any language in the `syslanguage` table, including self-localized and inactive languages (inactive languages are excluded from translation workflows). * **Spreadsheet Template:** Use the provided `ServiceNowGlossaryTemplate.xlsx` for glossary creation and uploads. It supports all ServiceNow AI Platform languages and self-localized languages by adding columns with language codes from `syslanguage`. * **Editing and Exporting:** Edit glossaries directly in the UI and export them as CSV or spreadsheet files to share with stakeholders or translation providers. * **Language Activation:** Activate languages by installing language plugins or create custom language records for unsupported languages. ## Practical Guidance * Plan glossaries to align with your organizational structure and translation needs. * Each glossary can contain between 50 and 1500 rows as a general guideline. * Do not modify header rows for certain supported languages (Brazilian Portuguese, French-Canada, Traditional Chinese) to ensure proper import mapping. * Leave translation fields blank for languages you do not intend to use. ## Benefits for ServiceNow Customers By using Language Asset Management, customers can centrally manage terminology and translations, ensuring accuracy and consistency across localized content. The ability to handle multiple glossaries and contextual translations helps tailor language assets to specific business units or locales, improving communication clarity and user experience in multilingual environments. Enhance localization in your instance with Language Asset Management in Localization Workspace. You can upload glossaries to Language Asset Management for editing and storage. ## Glossaries in Language Asset Management {#lw-language-asset-management__section_xbm_j2j_g3c} From version 3.0.0, the Language Asset Management area of Localization Workspace enables you to upload glossaries, which are lists of terms with translations that you provide. Each source term in a glossary can have translations into multiple languages. You can create multiple glossaries. In the Australia release, glossaries are available for storage and editing only. When planning your glossary assets, consider the following points. * You can have more than one glossary in Language Asset Management, so you can organize your glossaries according to business unit, function, or locale. * Each glossary can be subdivided or filtered using the Product/Service category. * One source term can be listed under different Product/Service or Part of Speech categories. A source term repeated in two different categories is considered to be two different records, so different translations can be assigned to each occurrence of the term per category. This enables a term to be translated differently depending on the context. * Translations assigned to source terms can be provided for any language listed in the sys_language table, including self-localized languages. * The included spreadsheet template (ServiceNow_Glossary_Template.xlsx) must be used when creating a glossary. For details see [Upload glossaries to Language Asset Management](https://www.servicenow.com/docs/_cJAnGfHpo2v44uGmCX7hQ "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."). * Any editing or modification to the contents of existing glossaries can be done in the UI. For details see [Edit a glossary in Language Asset Management](https://www.servicenow.com/docs/E4Ek4kZovZLCaYzaR9R5xw "Edit the contents of your glossary in Language Asset Management. Modify existing terms and translations or add more terms."). * There is no upper limit to the number of rows in a glossary, but the general guideline is for each glossary to have between 50 and 1500 rows. {#lw-language-asset-management__ul_sk4_lzw_33c} In the spreadsheet template, columns are provided for all languages supported by ServiceNow AI Platform in the sys_language table. You don't need to provide translations for all languages. Clear out (leave blank) all values for any languages you don't plan to use. You can upload glossary translations for languages that are active = false in sys_language, but inactive languages are not available for translation workflows. You can include self-localized languages when uploading glossaries with the spreadsheet template. Create additional columns in the spreadsheet template for self-localized languages. For the label in the header row of the spreadsheet, use codes from the ID column of the sys_language table for the corresponding languages. Note: With the following supported languages, the import transform handles mapping of the spreadsheet's language code to the ID code in sys_language. Do not modify or update the header row of the spreadsheet template for these languages. * Brazilian Portuguese * French - Canada * Traditional Chinese {#lw-language-asset-management__ul_jtz_qpj_l3c} To activate languages in sys_language, [install language plugins](https://www.servicenow.com/docs/Y30JfDvzXwarUH9yXwYnZA "By default, the language supported by the platform is American English. You can activate plugins for other supported languages if you have the admin role."). To self-localize an unsupported language, see [Create a language record](https://www.servicenow.com/docs/M_d6LYPOSAlyWPWP6kyZmA "Add a record for a language not provided by an internationalization (I18N) plugin to associate new translations with."). * **[Upload glossaries to Language Asset Management](https://www.servicenow.com/docs/_cJAnGfHpo2v44uGmCX7hQ)** 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. * **[Edit a glossary in Language Asset Management](https://www.servicenow.com/docs/E4Ek4kZovZLCaYzaR9R5xw)** Edit the contents of your glossary in Language Asset Management. Modify existing terms and translations or add more terms. * **[Export a glossary from Language Asset Management](https://www.servicenow.com/docs/OK3aicTiPNScKYRDLWJPQQ)** Download your glossary as a CSV or spreadsheet file to share with stakeholders, reviewers, or third-party translation service providers.