Languages and translated content
Choose interface and content languages independently, then review localized results.
The language you use in the dashboard and the language your audience reads are different choices. You can ask for another output language without translating every workspace setting.
Set the working language
-
Open the language preference in Workspace / Settings where available.
-
Choose the dashboard or workspace language described by the control and save.
-
Check the resulting menus. If your interface differs from these English guides, use the equivalent page names or contextual Help.
Create content for another language
Open the composer and choose its content-language control, if shown, or state the language explicitly in your prompt. Include the target country or audience when vocabulary varies. For example: “Write in French for retailers in France; keep the product name unchanged.” Review names, dates, currency, calls to action and destination URLs. Translate meaning and tone, not just words. Hashtags should fit the audience; a translated English hashtag may have little local use.
Work across several markets
Keep market-specific brand examples in Brand Profile. Use separate workspaces where languages also require different accounts, teams or brand rules. Run a bulk plan for one clear language/account set at a time and inspect every destination before scheduling. Social reply drafts may follow the incoming message's language. Read the full conversation and check the translation before sending. Image text also needs a visual review after translation, since spacing and line lengths can change.