Using the Translation Studio
Translation Studio is the administrator's workspace for translating portal content into every language your customers use. It covers the full range of platform-managed text — entity labels, field labels and help text, picklist values, button labels, app names, menu item labels, custom labels, validation messages, layouts, and more — in a single page with a unified workflow.
This page is the overview. Detailed workflow pages cover the editor, bulk import, the REST API, and troubleshooting.
Where the Translation Studio Lives
The Translation Studio is at Setup > Manage > Translation Studio. The page is admin-only by default; administrators can delegate access by granting the Enable Translation Studio Access delegation to other internal users.
Supported Languages
Translation Studio works with every language enabled on the portal in Configuring Language Settings. Currently supported language codes:
| Code | Language |
|---|
fr | French |
de | German |
es | Spanish |
it | Italian |
pt | Portuguese |
zh | Chinese |
ja | Japanese |
ru | Russian |
pt-BR | Portuguese (Brazil) |
es-MX | Spanish (Mexico) |
A language must be active on the portal before translations for that language can be added.
What You Can Translate
Translation Studio organizes translatable items into 11 types. Each type covers one category of content and has one or more aspects — the specific properties within that item that can be translated.
| Type | What It Covers | Aspects |
|---|
| Entity | Entity label and plural label | Label, PluralLabel |
| Field | Field labels and help text on an entity | Label, Help Text (when present) |
| Picklist | Picklist option labels | (single value) |
| Button | Button labels and confirmation prompts | Label, Confirmation (when present) |
| Layout | Form titles, success messages, section names, related-list titles | Form Title, Success Message, section names, related list titles |
| RecordType | Record Type names and descriptions | Name, Description (when present) |
| ValidationRule | Validation rule error messages | (single value) |
| LookupFilter | Lookup filter error and window messages | Error Message, Lookup Message (when present) |
| App | Application names | (single value) |
| Tab (Menu Item) | Menu Item labels | (single value) |
| CustomLabel | Custom Label values | (single value) |
For full details on each type and its aspects, see Translating Portal Content.
How Translations Are Applied
When a portal user signs in, the platform serves the translated value for each item based on the user's language preference. If the user's language has no translation for an item, the master (English) value is used as a fallback. This means you can roll out translations incrementally — the portal stays usable even with partial coverage.
Two Ways to Translate
| Method | When to Use |
|---|
| Translation Studio editor (recommended for ongoing work) | Translate one type at a time, language by language. The editor can also suggest AI-generated translations you can review and accept. See Translating Portal Content. |
| Bulk CSV import (recommended for initial population or large updates) | Download current translations as CSV, translate offline (in-house or with an external service), and re-import. Uses the Data Import wizard. See Bulk Importing Translations. |
Programmatic access is also available via the Translation REST API v3.
Permissions
- Administrators have full access to Translation Studio.
- Internal users with the Enable Translation Studio Access delegation can use the Studio without being administrators. Grant the delegation on the user's Security Role (Setup > Security > Security Roles).
- Other internal and partner users cannot access the Studio. They only see the translated content at runtime.
Troubleshooting Tips
Where to Go Next
Translation Studio Checklist >>