Translation Studio Checklist
Use this checklist to set up Translation Studio end to end. Configuration lives at Setup > Manage > Translation Studio. Each step links to a detailed article.
Requirements
- Administrator, or an internal user with the Enable Translation Studio Access delegation.
- The target languages must be enabled in Configuring Language Settings.
- Decide whether you will translate in the Studio editor, bulk-import from CSV, or use the REST API.
Plan
☐ Pick the target languages. Decide which languages your portal needs first. Activate them in Language Settings before starting any translation work.
☐ Identify the types you care about. Not every portal uses every type. Prioritize Apps, Tabs, Custom Labels, and frequently visited Entity and Field labels. Translate validation and lookup messages once basic UI is covered.
☐ Decide on a workflow. Small in-house translation effort → Studio editor. Large initial population or external translator → bulk CSV import. Programmatic / pipeline → REST API.
Configure Access
☐ Confirm administrator access. Administrators have access automatically.
☐ Delegate to non-host internal users (optional). Add the Enable Translation Studio Access delegation (on the user's Security Role) to internal users who will help with translation work.
Translate
☐ Translate via the Studio editor Pick a language and a type, work through items in the navigation tree, save translations as you go.
☐ Or import a CSV via the Data Import wizard Download the translation template, edit offline, upload to Data Import with the Translation Studio target.
☐ Or use the REST API. See Translation REST API v3 in the Developer Guide for the full programmatic surface.
Test
☐ Test as a user in each target language. Use Login As or a test user account whose language preference matches the language you translated. Confirm the translated values appear where you expect.
☐ Spot-check fallback behavior. Untranslated items fall back to the master (English) value. Confirm the user still sees a usable portal even with partial coverage.
Maintain
☐ Schedule periodic reviews. As new entities, fields, and Custom Labels are added, the translation backlog grows. A monthly review keeps coverage current.
If You Run Into Issues
☐ Translation Studio Troubleshooting Symptom-by-symptom resolutions for missing languages, missing items, outdated flags, and bulk import errors.
<< Using the Translation Studio | Translating Portal Content >>