Choose a Fixed Language

Boarbs supports multiple application languages, but it does not currently expose an organization-level toggle that forces one fixed language for the public portal.

So the practical goal today is consistency, not hard enforcement.

How Language Works Today

A few parts of the experience behave differently:

• signed-in users can choose their personal app language
• workspace content such as board names, roadmap names, and comments uses the wording you write
• public portal routes themselves are based on the workspace domain, not a special per-workspace language switch

Personal Language Settings

Signed-in users can change their own interface language from Account settings.

That is useful for the internal app, but it is not the same thing as forcing one public portal language for every visitor.

The Best Current Practice

If you want a consistent public language, do this deliberately in your content:

• write board names in one language
• write roadmap names and descriptions in the same language
• keep public comments customer-facing and consistent
• avoid mixing two languages in one public board unless that is truly your audience strategy

In practice, the language of your content matters more than the UI chrome.

Where Inconsistency Usually Starts

Teams usually create language drift when:

• one board is named in English and another in German
• roadmap columns use different terminology than statuses
• public comments are written ad hoc by different teammates
• support replies link into a portal that uses different wording than the product itself

A Simple Standard to Adopt

Pick one public language standard for:

• board names
• board descriptions
• roadmap names
• public comments
• release-note links around the portal

Document that standard internally so the team writes in the same voice.

When You Might Not Want a Fixed Language Anyway

If your product serves multiple language groups, forcing one language everywhere may not even be the best experience.

In that case, the better strategy is often:

• keep the portal structure simple
• use clear naming
• deep-link users from language-matched emails or docs

What This Guide Is Really Solving

Today, this guide is about editorial consistency more than a product toggle.

That is still valuable, because users feel inconsistency long before they ask whether a formal “fixed language” switch exists.

Next Steps

• Customize Your Portal — Keep wording and structure aligned with the rest of the public experience
• Deep Link Into Feedback — Send visitors from language-matched surfaces into the right Boarbs page
• Portal — See how the public experience behaves