> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/admin-guide/profile/org-settings/translations/multi-language-translation-support/enabling-and-configuring-language-support.md). # Enabling and configuring language support Unifize’s Language Support feature allows organizations to localize the platform for global teams, enabling users to interact in their preferred language and enhancing usability, adoption, and collaboration across regions. This guide helps administrators set up and manage language support across the organization. *** ### What is Language Support? Language Support in Unifize consists of three core elements: 1. **Primary Language** – The default language of the Org and the source of truth for all translations. 2. **Supported Languages** – A list of additional languages available for users to choose from. 3. **Preferred Language** – The language selected by each user individually via their Preferences. *** ### Steps to Enable Language Support ### 1. Set the Primary Language The **Primary Language** is the default language for your Unifize Org. All application content and custom fields are initially created in this language. * Each Org can have only **one Primary Language**. * This language becomes the **source of truth** for all translations. * It is used by default for users whose preferred language is not supported. > ⚠️ *The Primary Language is set during Org setup and cannot be changed once established.* *** ### 2. Add Supported Languages You can add multiple **Supported Languages** from our list of 26 languages to make Unifize accessible in other languages. Below is the list of 26 languages you can choose from: Unifize now supports the following 26 languages for the application UI and custom fields: 1. English (Primary language) 2. Chinese 3. Spanish 4. Portuguese 5. Russian 6. German 7. Korean 8. French 9. Turkish 10. Vietnamese 11. Italian 12. Thai 13. Burmese 14. Polish 15. Dutch 16. Romanian 17. Malay 18. Filipino 19. Ukrainian 20. Indonesian 21. Swahili 22. Greek 23. Czech 24. Hungarian 25. Serbian 26. Danish > 🌐 *Supported Languages can be added or removed at any point by contacting your Unifize Account Manager.* *** ### 3. Grant Access to the Translation Editor The **Translation Editor** allows authorized users to view and manage translations. #### To configure permissions: {% @arcade/embed flowId="8Y1ESo64x2J4sga8FODB" url="" %} > 🔐 *By default, these permissions are granted to Admins and can be customized as needed.* *** ### 4. Use the Translation Editor (for Admins) Admins can customize translations of UI elements, custom fields, and descriptions. #### To use the editor: {% stepper %} {% step %} Navigate to **Org Settings → Translations**

Profile > Org Settings > Translations

{% endstep %} {% step %} Select the language to edit from the dropdown
{% endstep %} {% step %} Use **Progressive Filters** to navigate to specific areas of the app (e.g., Forms, Processes)
{% endstep %} {% step %} Use the **Search Bar** to locate specific text
{% endstep %} {% step %} Edit fields inline in the **Translated Language** column
{% endstep %} {% step %} On hover, use the **Refresh translation** icon to restore default translations if needed
{% endstep %} {% endstepper %} > ✅ *Translations are auto-saved and applied immediately upon editing.* *** ### Best Practices * Keep your **Primary Language consistent** for process-wide uniformity. * Encourage users to set their **Preferred Language** via the **Profile → Preferences** menu. * Regularly review and update translations to ensure quality and consistency. * Use the **Search and Filters** within the Translation Editor to manage large translation datasets efficiently. *** ### Limitations & Considerations * Some UI elements may appear misaligned in certain languages. * Not all content is translatable (e.g., chat messages, process titles, uploaded documents). * Auto-translations rely on third-party translation services; manual review is recommended for critical fields. *** ### Conclusion By enabling and configuring Language Support, Admins empower global teams to work in the language they’re most comfortable with—boosting adoption, productivity, and collaboration. With easy-to-use tools and granular permissions, Unifize’s language support is flexible and admin-friendly. > 💡 **Related Articles** > > * \[[Using the Translation Editor](/admin-guide/profile/org-settings/translations/multi-language-translation-support/using-the-translation-editor-to-customize-ui.md)] > * \[[Managing User Language Preferences](/admin-guide/profile/org-settings/translations/multi-language-translation-support/managing-user-language-preferences-at-scale.md)] > * \[[What Gets Translated vs. What Doesn't](broken://pages/UUOirg7M9vK5HbDveV6s#major-releases)] --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.unifize.com/admin-guide/profile/org-settings/translations/multi-language-translation-support/enabling-and-configuring-language-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.