Published at: 2026-09-17
Internationalization configuration quick start
Before you begin
Confirm the internationalization products, rollout capabilities, and administrator permissions purchased or enabled for your enterprise. Entry points can differ by enterprise version. If an entry point is missing, check product enablement and role permissions instead of inferring behavior from another enterprise’s interface.
Assign internationalization management permissions
A system administrator can go to Setup > Role Permission Management > Management Function Permissions > Permission Settings, then search for or expand Internationalization to assign these permissions to management roles:
| Management permission | Primary purpose |
|---|---|
| Translation Workbench | Access Translation Workbench and maintain, import, export, and synchronize system terms |
| Language Settings | Manage enterprise language scope and language configuration; maintaining object and field names also requires access to the relevant object-management entry point |
| Data Translation Settings | Enable data-level multiple-language support for eligible objects and fields |
| Multiple Currency Settings | Enable multiple currencies and maintain transaction currencies and enterprise exchange rates |
The built-in System Administrator role has these permissions. Other management roles can receive them individually according to responsibility. Select All only selects all four permissions; it is not a separate permission. Compliance Settings is not in the Internationalization permission group. It still requires access to Enterprise Settings > Compliance Settings and permission to manage the target objects and fields.
Recommended configuration order
- Define the business scope: List launch countries or regions, employee languages, business time zones, transaction currencies, and address-collection methods.
- Establish geographic master data: Maintain countries, regions, administrative divisions, and regional formats. Confirm standard codes and enablement status.
- Set enterprise defaults: Set the default language, time zone, and regional format, then define the options employees can select.
- Configure multilingual content: Translate system terms such as object names, field names, and layouts, then decide which business-data fields require multiple languages.
- Configure currencies and exchange rates: Confirm the base currency, enable transaction currencies, and maintain rates. Assess historical data before enabling the feature for an existing enterprise.
- Configure address formats: Define form order, required rules, and text composition for Dynamic Address fields by country or region.
- Validate by role: Use both administrator and employee accounts. Switch language, time zone, regional format, and currency, then validate create, edit, detail, list, export, and reporting scenarios.
Go-live checklist
- Enterprise defaults and personal overrides follow the expected precedence.
- Translations for custom objects, fields, layouts, and record types are synchronized and effective.
- Cross-day, daylight saving time, and cross-time-zone collaboration scenarios have been tested with actual dates.
- The business owner has confirmed the display and reporting rules for the base currency, transaction currencies, exchange rates, and historical records.
- Country and region codes, administrative divisions, and address formats have been tested with examples from each target country.
[!WARNING] Processing historical multi-currency data, enabling or disabling countries and regions, and changing administrative divisions can affect existing business. Validate changes in a test environment or with a limited data set, and retain change records before production use.