Enable community languages in the Admin Dashboard, see which organizer-written content can translate automatically for readers, keep brand and community terms consistent with the Localization Glossary, review or pin translations in Overrides, and finish the content you still enter by hand.
Bevy translates Bevy-generated interface copy into the languages your community enables. HQ admins still choose which languages are available, assign languages to chapters, and enter or pin translations for some customized content. When organizer-content translation is on for your community, much of the copy organizers write on events and chapter pages can also appear in the reader’s language without a separate manual export.
For the languages Bevy can serve and which product surfaces follow the reader’s language today, see Language Support for Bevy Products. Visitors and members choose the language they see in Choose your display language.
Enable languages for your community
- Sign in as an HQ admin.
- Open the Admin Dashboard.
- Go to Localization (languages and localization content live here).
- Identify the language or languages you want to enable. Confirm each language appears in Language Support for Bevy Products.
- Enable the language(s) for the instance using your community’s Localization settings.
Note: Only languages enabled on the instance can be assigned to chapters. After you enable a language, assign it on each chapter’s settings in the Chapter Dashboard.
Organizer content that can translate automatically
When Bevy has turned on organizer-content translation for your community, readers who view the site in a non-source language can see AI translations of the organizer-written fields below. Organizers keep writing in the source language; readers do not need a separate translation workflow for these fields.
| Organizer content | What readers can see translated |
|---|---|
| Event agendas and sessions | Session titles and descriptions on event pages (and related agenda surfaces) |
| Ticket types | Ticket names and descriptions in the event ticket list and purchase flow |
| Startups / companies | Company descriptions on event pages (company names stay as written) |
| Speakers and people | Job titles and bios on People blocks (personal and company names stay as written) |
| Chapter team | Team role titles; member bios when profile translation is also enabled for the community |
| Sponsors | Sponsor descriptions on event, chapter, and global sponsor blocks (sponsor names stay as written) |
| Media library | Media item titles and descriptions |
If readers still see English (or your source language) for these fields after languages are enabled, ask your Customer Success Manager whether organizer-content translation is on for your community. One community setting controls this set of content types — there are no separate per-type toggles for agendas, tickets, companies, or people.
Keep brand and community terms consistent
AI translations can protect your community’s own vocabulary and brand names so terms stay consistent across pages. Bevy automatically includes:
- Your site title (kept as written)
- Your community’s vocabulary labels (for example terms like Guild, Hub, or Chapter when your community uses them in the product UI)
When your Admin Dashboard includes a Glossary tab under Localization, you can also add curated rules:
- Open Admin Dashboard → Localization → Glossary.
- Review Automatic terms for the language you care about (site title and vocabulary pins).
- Select Add term.
- Enter the Term, choose All languages or one active language, and pick a rule:
- Keep as written — protect a name or brand string from being translated.
- Always translate as — lock the exact translation to use.
- Select Save.
Note: Glossary rules apply to new AI translations. If you do not see Glossary, or a notice says the glossary is not turned on yet, you can still prepare terms (when the tab is available) and ask your Customer Success Manager to enable the glossary for your community.
Chapter apply and join forms
Chapter apply and join form labels follow the language of the page the visitor is viewing — not only the browser’s preferred language. When the page is shown in a supported language, the apply/join modal uses that same language.
Review or pin translations in Overrides
Some community-authored strings can translate automatically and also appear in Localization → Overrides, where HQ admins can review the current translation and pin an exact wording per language. Overrides is a different screen from Localization → Content.
Open Admin Dashboard → Localization → Overrides, then pick the section that matches the content:
| Content type | Where you review or pin translations |
|---|---|
| Forum board names and descriptions | Admin Dashboard → Localization → Overrides → Forums |
| Page menu titles, and page titles used when a menu title is blank (for example some footer quick links) | Admin Dashboard → Localization → Overrides → Page nav |
| Customized community assistant chat input placeholder (and other Style copy rows listed there) | Admin Dashboard → Localization → Overrides → Style copy |
- Select the language you want to review.
- Find the row for the board, menu label, page title, or style-copy string.
- Edit the translation if you need exact wording.
- Select Save for that row.
A saved override stays until you clear it or the source English changes in a way that flags the row for review. If you do not see Overrides, ask your Customer Success Manager whether it is available for your community.
Some site-level copy — for example the short footer description and cookie-banner text — can also follow the reader’s language when Bevy has turned that translation on for your community. Those strings are not entered under Localization → Content, and they are not listed in Overrides today. If they stay in the source language on the public site, ask your Customer Success Manager.
Content you still translate yourself
HQ admins remain responsible for entering translations for customized localization content that is not covered by automatic organizer-content translation or Overrides. Common examples:
| Content type | Where you enter translations |
|---|---|
| Region names, event type names, event tags | Admin Dashboard → Localization → Content |
| Global form questions and responses (pre-order, post-event, post-event team) | Admin Dashboard → Localization → Content |
| Page Builder canvas copy you manage in localization mode | Admin Dashboard → Localization → Page Builder |
| Automated and system email copy you customize | Email editors in the Admin Dashboard |
- Gather the English (or source-language) copy you need translated.
- Translate it with your preferred method (in-house experts, a localization vendor, or another approved process).
- Enter the translations in the locations in the table above.
- Assign each chapter a language in that chapter’s settings. Only languages enabled on the instance are available.
Tip for organizers: Write clear source-language titles, bios, ticket names, and sponsor blurbs on the event or chapter. When organizer-content translation is on, readers in other enabled languages see those fields in their language — you do not paste separate translations for each agenda session or ticket type.