Enable Translation Workbench and add a language so translators can start localizing your customizations. You need a multi-language org and the Manage Translation permission, which the System Administrator profile already has.
- Enable the workbench
From Setup, enter Translation Language Settings in the Quick Find box and select it. On the welcome page, click Enable. The feature appears only if your org supports more than one language.
- Add a language and translators
On the Translation Language Settings page click Add, choose the target language, and assign one or more users as translators. Leave Active unchecked while translation is still underway.
- Enter translations
Go to Setup, open Translate, choose the language and a setup component such as Picklist Value or Custom Label, expand the tree, and type the translated text next to each source value. Filter to untranslated or out of date items to track progress.
- Activate the language
Once translators confirm every string is filled in, return to Translation Language Settings, edit the language, and select Active. Users assigned that language now see your translated customizations.
Makes a language visible to end users. Keep it off until translation is complete so users do not see gaps or untranslated strings.
The users responsible for entering strings for a language. Assign one clear owner per language to avoid conflicting terminology.
On the Translate page, selects which metadata type you are translating, such as custom labels, picklist values, record types, or validation rule error messages.
Lets you replace strings already supplied by a second-generation managed package or the default language, instead of adding a brand new language translation.
- Translation Workbench is unavailable in single-language orgs. Your org must support more than one language before the Enable option appears.
- Activating a language before translators finish exposes untranslated or partial strings to those users immediately.
- The workbench translates customizable metadata, not record data or the standard UI. Standard labels come from the language pack based on the support level.
- Editing a source value can mark its existing translation out of date, so translations need maintenance every time customizations change.