> ## Documentation Index
> Fetch the complete documentation index at: https://orgo.space/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Languages
> Enable multiple languages so members use Orgo in their preferred language
Orgo's interface is available in 11 languages. You choose which languages are available, set a default, and members pick their preference. The entire interface — menus, buttons, labels, system messages — switches to their language instantly.
**Settings → Customization → Languages**
Requires **Tenant Admin** permissions.
***
## Setting up languages
Go to **Settings → Customization → Languages**. You'll see a list of all supported languages with toggle switches.
Toggle on each language your organization uses. Each toggle controls whether that language appears in the language picker for members.
Select the primary language from the dropdown at the top. This is the language new members see when they first access the platform, and the fallback when no preference is set.
Toggle on the language selector so it appears in the interface. When enabled, members see a language dropdown in their profile area to switch languages.
Click **Save** to apply. Changes take effect immediately for all members.
***
## Supported languages
| Language | Code | Notes |
| ---------- | ---- | ------------------------- |
| English | en | Most complete translation |
| Romanian | ro | Fully translated |
| French | fr | Fully translated |
| German | de | Fully translated |
| Spanish | es | Fully translated |
| Italian | it | Fully translated |
| Portuguese | pr | Fully translated |
| Dutch | nl | Fully translated |
| Slovak | sk | Fully translated |
| Ukrainian | ua | Fully translated |
| Bulgarian | bg | Fully translated |
The platform interface (menus, buttons, system messages) is fully translated in all supported languages. User-generated content (discussion posts, event descriptions) stays in the language it was written in.
Only enable languages your members actually speak. Extra languages clutter the language picker. You can always add more later without affecting existing members.
***
## How members choose their language
Members change their language from the **profile dropdown menu** in the top-right corner of the interface. The interface updates immediately — no logout required.
For first-time visitors, the system detects language automatically from:
* **Browser language settings** — matched against your enabled languages
* **Previous selection** — saved in the browser if they've visited before
If neither matches an enabled language, the platform falls back to your default language.
***
## What gets translated
| Content | Translated? | Details |
| ------------------------------------------------------ | ------------ | -------------------------------------------------- |
| **Platform interface** (menus, buttons, labels, forms) | Yes | Fully translated in all 11 languages |
| **System emails** (notifications, confirmations) | Yes | Sent in the member's chosen language |
| **User-generated content** (posts, events, files) | No | Stays in the original language |
| **Custom labels** (your terminology overrides) | Per-language | You provide translations for each active language |
| **Welcome message** | Per-language | Write separate versions per language |
| **Registration form** | Yes | Follows the visitor's detected or default language |
***
## Multi-language labels
If you've customized labels (e.g., "Members" → "Scouts"), you need to provide translations for each enabled language. Without a per-language override, the customized label falls back to the default language version.
See [Labels & Terminology](/platform/customization/labels) for the full setup process.
***
## Real-world example
> **Scenario**: A Swiss non-profit operating across French-speaking and German-speaking cantons, with 2,000 members.
1. **Enable** French and German. Leave other languages disabled.
2. **Set default** to French (60% of members are French-speaking).
3. **Enable the language switcher** so German-speaking members can switch.
4. **Customize labels** in both languages: "Membre" (FR) / "Mitglied" (DE) instead of "Member".
5. **Write the welcome message** in both French and German versions.
Result: French-speaking members see everything in French by default. German-speaking members switch once, and their preference is remembered. System emails (event reminders, fee notifications) go out in each member's chosen language.
***
## Troubleshooting
Enable both languages and set the one with more members as default. System-generated content (menus, emails) translates automatically. For user content (discussion posts, event descriptions), you have two options: post in both languages, or pick one common language for shared content. Many bilingual organizations post announcements in both languages.
They can change it from their **profile menu** in the top-right corner. If new members consistently get the wrong default, check that your default language setting matches the majority language. Also verify that the language switcher is enabled so members can change it themselves.
The default language only affects new members and visitors without a saved preference. Existing members keep their previously chosen language. They need to switch manually from their profile menu.
If you've customized labels, you need to provide a translation for each enabled language separately. Go to **Settings → Customization → Labels**, switch to the language that's missing, and add the override. Labels without an override fall back to the default language version.
***
## Related
* [Labels & Terminology](/platform/customization/labels) — Custom terminology with per-language translations
* [Dashboard Welcome](/platform/customization/dashboard-welcome) — Write welcome messages per language
* [Branding](/platform/organisation/branding) — Visual customization (logos, login background)