Skip to main content
Your community might span the globe. Add languages so users can engage in the language they’re most comfortable with. Then manage all the translation strings from one place—with search, filtering, and import/export tools.
Settings Location: Navigate to Control Room > Settings > Languages & Translation to manage languages and translations.

​
Adding Languages

Click Add Language to bring a new language into your community. The Language Configurations table shows all your languages:

Language

Language name (Spanish, French, etc.)

Code

Language code (es, fr, de)

Status

Enabled or Disabled for users

Actions

Click Edit to translate

​
Default Language

Set your primary/fallback language at the top. This is the language that appears when:
  • A translation is missing
  • Users haven’t selected a language yet
  • A translation key doesn’t exist
Usually this is English, but it can be whatever makes sense for your organization.

​
Editing Translations

Click Edit on any language to start translating. You’ll see two sides working together:
  • Left: Translation Tree
  • Right: Filter & Tools
A tree structure showing all translation keys organized by feature:
  • root — Core platform strings
  • achievements — Achievement-related text
  • card, carousel, completed — Specific UI components
  • actions — Challenge action labels
  • questions, title, view — Content structure
  • And many more organized by feature
Each category shows how many items need translation in parentheses. Click to expand and see individual strings to translate.

​
Filter & Translation Tools

The right panel gives you control over what you see and how you work:
Type to search by translation keys or values. Great for finding a specific string without scrolling through the whole tree. (Ctrl+F)
Enable or disable this language. Users won’t see disabled languages, even if they’re 50% translated. Use this to hide a language while you’re still working on it.
Hide default/untranslated items. Only show strings you’ve actually customized (where your translation differs from the defaults). Useful for auditing what you’ve changed.
Hide completed translations. Only show keys that still need work. Perfect for tracking what’s left to do and staying focused on gaps.
Display the internal reference ID next to each translation key. Useful if you’re working with external translators or need to track specific strings.
Download a CSV file with all translation keys, current values, and status. Send this to your translator or use it as a reference. Click Download Translation Guide (CSV) to export.
Upload a CSV with translations you’ve completed elsewhere. Format: Reference ID, Path, Value. Great for batch importing translations from external translators.
Restore all translations in this language back to the defaults. Useful if translations got messed up and you want to start fresh.
Reference legend showing translation status indicators:
  • Default/Unchanged — Uses the default value from the primary language
  • Custom Override — You’ve customized this translation
  • Needs Translation — Not yet translated

​
Making Translations

For each key you translate:
  1. You see the original text (from your default language)
  2. Enter the translated text
  3. The status updates to show it’s been customized
  4. Missing translations stay as the default until you fill them in
It’s straightforward—just edit the values as you go through the tree.
Pro tip: Use “Show Needs Translation Only” to see just the gaps. Then work through them systematically. Much faster than scrolling through everything.

​
Translation Workflows

Pick the approach that works best for you:

Translate as You Go

Add a language and gradually translate strings as you create new content. No big project—just add translations when you add content.

Bulk Import

Download the Reference Guide, send to a professional translator, then import the completed CSV. Best for large translation projects.

Search & Fix

Use Search to find specific strings, translate them, move on. Great for spot fixes and incremental improvements.

​
Best Practices

Translate your organization name, key navigation labels, and most popular challenges first. Users understand partial translations better than broken ones. Get the 20% done that matters most.
If possible, have native speakers review translations. Automated translation works but misses context, tone, and cultural nuance. It’s worth the effort.
After translating, switch your language and check how things look in the actual UI. Truncation, formatting, and context matter—something might read fine in isolation but look broken on screen.
The same term should always translate the same way. Keep a simple glossary if you’re working with multiple translators. Consistency builds trust.
When you update content in your primary language, plan to update translations too. Mark language as Disabled while you catch up if needed, so users don’t see half-translated updates.

​
Quick Start

Get your community multilingual:
1

Set Default Language

Choose your primary language (usually English) at the top
2

Add Additional Languages

Click Add Language and select the ones you need
3

Start Translating

Click Edit and start translating strings in the tree
4

Use Filters

Use Show Needs Translation Only to focus on gaps
5

Download for Translators

If working with professionals, download the Reference Guide CSV
6

Test

Switch languages in the UI and verify everything looks right
Your community speaks many languages. Make each one feel right.