The first time I came across the "Localization Tool" in Docebo, I assumed it was strictly a feature for translating the platform into different languages like Spanish, French, or Japanese. But with a bit of out-of-the-box thinking, I discovered it is much more than a dictionary, it is a powerful tool for shaping the User Experience (UX).
While Docebo handles multi-language support beautifully, the real secret of the Localization Tool is the ability to use it to translate Docebo's default English into your organization's specific English.
Every piece of text you see in the Docebo UI,from button labels to menu items and status names, is tied to a "language key." By overwriting these keys, you can fundamentally shape the user experience to match your corporate vocabulary without writing a single line of custom code.
The Core Solution: Overwriting Language Keys
Instead of forcing your learners to learn Docebo's terminology, you can make Docebo speak your language. If your company calls training modules "Programs" instead of "Courses," you don't need to settle. You simply find the relevant keys and change them.
To access this tool, navigate to Admin Menu > Settings > Localization tool. Click on the language you want to edit, and you will be taken to an internal database where you can search for any text that exists in the platform. You can read more about this in the official Docebo documentation for managing the localization tool.
Gotchas / What to Watch Out For
There is one major rule when using the Localization Tool for UX changes: Keys are global.
As noted in the Docebo KB, a single language key can be used in several areas across the platform. For example, if you decide to change the word "Learner" to "Employee", keep in mind that external vendors, contractors, or partners logging into your system (especially if you use Extended Enterprise) will also see the word "Employee" in descriptions and UI elements. Always be cautious and test your changes from an end-user (Learner) account to ensure the new context makes sense everywhere, not just on the specific screen you tried to fix.
Popular UX Customization Use Cases
- Content Types: Changing the word "Courses" to "Modules", "Programs", or "Certifications".
- Corporate Branding & Terminology: Adapting terms like "Catalog" to "Learning Hub", "Academy", or "Knowledge Portal".
- Call-to-Action Buttons (CTA): Changing the text from "Enroll" to "Sign Up", "Start Learning", or "Register Now".
- ILT Status Management: Changing the "Suspended" status to "No Show" (which removes the course from the learner's active dashboard while accurately reflecting their absence without needing custom statuses).
Step-by-Step Configuration
- Go to the Admin Menu, find the Settings section, and click Localization tool.
- Find your active language in the list and click the Translate icon (the dictionary symbol) in its row.
- Use the search bar to find the exact text you want to change.
- Alternatively, use the Module dropdown to filter keys by specific platform areas (like "Course catalog" or "ILT").
- Edit the text in the translation column. The system saves your changes automatically.
When You Might Need a Different Approach (Bulk Updates)
If you are completely overhauling the platform's vocabulary (changing dozens or hundreds of terms), doing it one by one in the UI is tedious. Instead, use the Import/Export feature at the top of the Localization tool page.
You can export the entire language file as a spreadsheet (Excel/CSV), use "Find and Replace" in Excel to change every instance of "Course" to "Program," and then import the file back into Docebo, flagging the option to overwrite existing words. Just be careful not to modify the actual key column (the code the system reads) during your bulk edits!