Multi-language design with Translation Workbench and user language settings
Key Takeaway
Users see Salesforce and its customizations in their own language when they pick that language in their personal settings and Translation Workbench holds translations of custom field labels and picklist values. To prepare a language before users see it, add it as inactive, import translations as they arrive, and mark it Active only after all values are reviewed.
Multi-language design decides which language each user sees in Salesforce and how the org's own customizations get translated. The org has a default language, and each user can pick a personal language. Translation Workbench stores translations for things the org builds, such as custom field labels and picklist values. For a global Agentforce Financial Services rollout, a consultant combines these settings so users in each country can work in their own language.
Org default and personal language
Language and locale are separate settings. Language controls the language that objects, fields, settings, and user interface text appear in. Locale controls display formats for dates, times, addresses, phone numbers, and the commas and periods in numbers.
An admin sets the org-wide "Default Language", "Default Locale", and "Currency Locale" on the "Company Information" page in Setup. All new users inherit these settings.
Each user can change their own language, and optionally their locale, in Lightning Experience from their avatar, then Settings, then "Language & Time Zone". Users who don't change their language keep working in the org's default language.