Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryTTranslation Workbench
AdministrationIntermediate

Translation Workbench

A Salesforce setup tool that manages the translation of custom labels, picklist values, field names, page layouts, and other customizable text into multiple languages for organizations with multilingual users.

§ 01

Definition

A Salesforce setup tool that manages the translation of custom labels, picklist values, field names, page layouts, and other customizable text into multiple languages for organizations with multilingual users.

§ 02

In plain English

👋 Study buddy

Translation Workbench is a Salesforce setup tool for translating custom labels, picklist values, field names, page layouts, and other customizable text into multiple languages. It's how you localize your Salesforce org for users who work in different languages.

§ 03

Worked example

scenario · real-world use

Zephyr Books, a global book retailer, has Salesforce users in 14 countries. The admin uses the Translation Workbench to translate custom field labels, picklist values, page section headers, and validation-rule error messages into French, German, Spanish, Portuguese, Japanese, Mandarin, and Korean. Each user sees the org in their preferred language based on their Locale setting; the translations come from the Translation Workbench's master translation file. When the admin adds a new custom field Wholesale Tier, she also adds the translations in seven languages so global users see it in their own language. The Translation Workbench is the centralized localization toolset.

§ 04

Why Translation Workbench matters

Translation Workbench is a Salesforce setup tool that manages the translation of custom labels, picklist values, field names, page layouts, and other customizable text into multiple languages, enabling multi-language Salesforce deployments for global organizations.

Translation Workbench is essential for any Salesforce org serving users in multiple languages. Administrators or translators use it to provide translations for every piece of customized text, ensuring users see Salesforce in their preferred language. Mature multi-language deployments invest in translation management as ongoing work since new customizations need translations.

§ 05

How to set up Translation Workbench

Translation Workbench is the i18n tooling for Salesforce — translates Custom Labels, picklist values, field labels, and validation rule messages into supported languages. Without it, your UI is stuck in the org's default language.

  1. Open Setup → Translation Workbench → Translation Settings → Enable

    First-time enablement. Pick the org's translatable languages.

  2. Setup → Translation Workbench → Supported Languages → Add

    Multi-select languages your org supports — French, Spanish, German, Japanese, etc.

  3. Assign Translators per language

    Translation Workbench → Translators → assign users by language. Each translator can edit only their language.

  4. Open the Translation Workbench Translate page

    Setup → Translation Workbench → Translate.

  5. Pick the Language and Setup Component

    Component: Custom Field, Picklist Value, Custom Label, Validation Rule Message, etc. Each component type has its own translatable strings.

  6. For each row, type the translation

    Or import a translation file (XLF format). Inline editing is fine for small orgs; XLF round-trip for large ones.

  7. Save

    Translations are stored. Users with the language set as their personal language now see the translated UI.

Key options
Supported Languagesremember

Up to 50+ supported languages. Each adds a translator dimension.

Translatable Componentsremember

Custom Fields / Custom Labels / Picklist Values / Validation Rule Messages / Layouts (sections) / Standard Field Help Text / etc.

Inline editor vs XLF importremember

Inline for small orgs; XLF for translator workflows.

Translators per languageremember

Users authorized to edit translations for a specific language. Read-only otherwise.

Gotchas
  • Hard-coded UI strings (in Apex / LWC) can't be translated by Translation Workbench. Use Custom Labels for any string a user might see.
  • Picklist Translation hides the original value from the user but stores it under the original. Reports built on picklist values still show the API name unless the report is run by a translator-language user.
  • Translation Workbench is org-wide. Per-Experience-Cloud-site translation requires a separate config on the Experience site itself.
§ 06

How organizations use Translation Workbench

Vertex Global

Uses Translation Workbench to maintain their org in 12 languages.

NovaScale International

Treats translation as ongoing work with every new customization needing translations.

BrightEdge Solutions

Assigns translation responsibility to regional admins through Translation Workbench.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Translation Workbench.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

🧠 Test your knowledge

Q1. What is Translation Workbench?

Q2. What can be translated?

Q3. Is translation a one-time task?

§

Discussion

Loading…

Loading discussion…