A support team based in three countries shouldn't have to solve "which languages do we support" separately for the mobile app, the web forms, and every teammate's personal account. Workspace Language Settings let an administrator set that list once, and every other surface in MergePoint draws from it.
1. Set your workspace's supported languages
From Workspace Settings → Language & Region, an admin picks the languages the organization operates in and chooses a default language. This isn't a form-level setting — it's the shared pool everything else in the workspace pulls from.
2. It governs the mobile app's available languages
The same list controls which languages the mobile app can offer. Add a language here and it becomes available on mobile without any separate mobile-specific configuration.
3. It's the source list for every form
Form authors can only add a language to an individual form from this workspace list (or, if a specific form needs something outside it, a form-only exception). This keeps the organization from ending up with a different, inconsistent set of "supported" languages on every form — there's one list, set centrally, that every form draws from. Each language row also shows how many forms currently use it, so an admin can see the impact before removing one.
4. It's the source list for personal accounts too
When a teammate sets their own account's language under Personal Settings → Language & Locale, the choices offered are filtered to this same workspace list — so nobody ends up with a personal UI language the rest of the org doesn't actually support or translate content into.
Best practices
- Set this list before rolling out forms to multiple regions — it's much easier to start with the right set of languages than to add one later and have to catch every form up.
- Check the per-language form count before removing a language — removing one that's still in active use will affect those forms' language picker.
- Choose a default language your whole org can read — it's what respondents and teammates see before any language preference is set.
- Use form-only languages sparingly — prefer adding a language to the workspace list if more than one form or the mobile app needs it.