Translation Management
The Translation Management module helps you manage multilingual content in your application. It supports translations for strings and schema and ensures that every user experiences the platform in their preferred language. It brings together automation, traceability, and scalability, all while maintaining a smooth and consistent user experience.
When a user accesses a page, the platform checks their user-level locale setting. If one is found, it uses that locale to display translated content. If no user-level preference exists, the system falls back to the organization-level locale. And if neither is set, the default fallback—English (US)—is used.
Supported Locales
Translation Management supports the following languages, with English (US) set as the default and fallback. The full list includes:
|
English (US) |
Italian (Italy) |
|
English (UK) |
Spanish (Spain) |
|
French (France) |
Portuguese (Portugal) |
|
German (Germany) |
Dutch (Netherlands) |
|
Swedish (Sweden) |
Japanese (Japan) |
|
Mandarin (China) |
Automatic Translation and Content Propagation
Translation Management brings all your translation needs into a single place. It intelligently detects new or updated content and initiates the translation process automatically, without requiring manual effort. For example, if a new field label or message is added, the system identifies it and applies translations based on the active locales in your organization. This automation saves time and reduces manual errors. If you are making changes manually, the platform gives you control—it asks whether the update should apply only to the current locale or be propagated across all active locales. This flexibility helps you tailor the translation strategy to your specific use case.
Each translated entry is logged for traceability. This means you can view the entire change history, see who made a change, and when it was made.Importantly, system-generated translations for standard schema and strings are read-only, ensuring that critical content remains stable and unaltered.
Managing Locales
Administrators can manage which locales are active for their organization through the Translation Management > Locale Setup interface. While English (US) is always active and cannot be removed, additional languages can be added one at a time to maintain system stability. If a locale is no longer needed, it can be removed—but keep in mind that doing so also deletes all its associated translations. Any users affected by this change will automatically revert to the organization's default locale or English (US) - if the organization's default is not available.
Organization (Org) and User Locale Settings
Administrators can set an organization-level primary locale from the list of active languages. This sets the default experience for users who have not specified a user-level locale. If no locale is set at the user level, the system considers the org-level locale for the translation. If no preference is set at either the organization or user level, English (US) is used as the default fallback language.
Activity History
Translation Management maintains a detailed history of every translation, allowing you to access all activity history of a translated string. This audit history provides visibility into what changed, when it changed, and who made the change.
Translation Management UI Overview
The Translation Management user interface provides a simple and organized way to manage translations. It is organized into separate views for string translations and schema translations. You can filter and sort records by locale and module to narrow down results, and a search option is available to quickly locate specific entries using the translation Key. Each translation entry displays important metadata, such as the key, translation, the type of translation, the module and locale it belongs to, last updated date, and the name of the person who made the change.
Schema translations are managed automatically by the system whenever custom objects or fields are added. These translation entries cannot be deleted manually, but administrators can update them as needed.
For string translations, administrators can add up to 10 unique custom entries at a time.
