Site Structure is the central place to manage your community's language structure and language settings.
Use Site Structure to choose how languages fit into your community structure. You can keep a single static language, use static-language subcommunities, use AI Languages, or use a hybrid structure.
IMPORTANT: Configuring a non-default static language does not create a separate destination by itself. In Site Structure, you can create static-language subcommunities for separate member-facing experiences, or keep languages in a shared global experience with the same content and apply separate layouts and Style Guides where supported.
Manage languages in Site Structure
- Access the Dashboard.
- Open Site Structure.
- Use the language-structure controls to choose the language model for your community and configure the available languages.
Site Structure manages the relationship between your global community area, configured static languages, AI Languages, and language subcommunities. A configured non-default static language does not create a separately navigable destination by itself. Use a static-language subcommunity for a separate member-facing destination, or keep languages in the shared global experience with the same content and apply separate layouts and Style Guides where supported.
Enable languages
To be deprecated with Release 2026.017: The legacy Translation Settings path in this article is being replaced by Translation Settings and Site Structure. This temporary note will be removed after Release 2026.017 is available in all customer environments. See Release 2026.017 release notes.
The Translation Settings page features dozens of language options. Scroll down the page and toggle on any languages you want available as a community default in the Default Language dropdown. If there's a language you want to use that's not displayed in the menu, you must enable it first.
The languages enabled here tie into other aspects of your community as well. Refer to the section below to learn more.
What happens when you enable a language?
Apart from making it available as a default language option, as you learned above, enabling a language also:
- Exposes it as a locale option for Knowledge Bases
- Makes the language available for UI/“Multilingual” interface switching
- If the Multilingual addon is enabled, any languages you enable in Translation Settings become choices users can pick in the community footer to translate interface elements (navigation, labels, menus) into their preferred language.
- These language options only appear to logged-in users, and their selection is remembered for future logins.
- This affects interface text only, not user-generated content.
- Makes the language available for KB translation & machine translation workflows
- For manual or machine translation of KB articles, you first enable the languages you want to translate into via Translation Settings.
- Once enabled, you can assign a Translation Service Provider (e.g., Google Translate or DeepL) per language and use it as a target language in the Machine Translation modal for KB articles.
- Enables that language in other language-aware features (e.g., email templates)
- Email Templates can store localized Subject/Body/Footer text for each of your enabled languages. When a user has a preferred language, the system uses that language’s version; otherwise it falls back to the community default language.
Supported languages
Click here to see the full list of supported languages.
Multiple languages
Customize translated terms
After you configure languages, use Settings > Technical > Translation Settings to define preferred wording for system terms and translated content.
See Override System Terms with Custom Translation Terms for the complete workflow. For custom terms applied to AI-translated user-generated content, see AI Translations.
If you’d like to use more than one language, start with Language Translation Overview to review the available language-management options. Then open Site Structure to choose and configure the structure that fits your community.
Remember that a configured non-default static language does not create a separate destination on its own. Use a static-language subcommunity for a separate member-facing destination, or keep languages in the shared global experience with the same content and apply separate layouts and Style Guides where supported.
For AI Languages details, see AI Translations.
