Skip to main content
Best Answer

Choosing language/translating Course additional fields

  • Nov 19, 2026 3:07 PM UTC
  • 1 reply
  • 2 views

When creating a New Additional field in Course management, it is as within many other features, possible to make the Field name to be in several languages of choice.

But when adding the additional field to a course, it seems like its not possible to add text in several languages, as I see no button, globe or switch to change and make it able to translate the field.

 

On summary and languages you can change and manage translations, but when changing to for example from Norwegian to English UK, it seems that it doesnt apply when clicking into Course additional fields afterwards.
 


Anyone who knows how to be able to translate within an Additional field/text field or if it’s even possible at all?

Best answer by Moshe.Machlav

You are not missing a button - unfortunately, Text and Free text Course Additional Fields cannot be translated at the course level.

When you create a Course Additional Field, Docebo lets you translate the field label (and the predefined options if it is a Dropdown field). However, once you populate a Text or Free text field inside a course (Properties > Course additional fields), it only stores a single static value. The Manage translations feature under Summary and languages only applies to the course Title, Short description, and Description, which is why switching from Norwegian to English UK there does not carry over.

In multilingual organizations I've worked with, the pattern that holds up best depends on what kind of data you are trying to display:

  • If the values are recurring or standardized (like audience, difficulty level, or category): Switch from a Text field to a Dropdown additional field. Because you can translate each dropdown option when configuring the field, learners will automatically see the selected value in their profile language.

  • If it is course-specific text that learners need to read in their own language: Move that content into the Course Description (or Short Description) under Properties > Summary and languages. That area natively supports multi-language translations (both manual and AI-assisted) and dynamically matches the learner's profile language.

  • If it is a brief, unique value that must stay in a text field: The only native fallback is formatting both languages in the same string (e.g., Norwegian / English), though this only scales cleanly if you support two languages.

You can check the full breakdown of how these two areas behave in the Docebo Help Center:

 

View original

1 reply

Moshe.Machlav
Guide I
Forum|alt.badge.img+2

You are not missing a button - unfortunately, Text and Free text Course Additional Fields cannot be translated at the course level.

When you create a Course Additional Field, Docebo lets you translate the field label (and the predefined options if it is a Dropdown field). However, once you populate a Text or Free text field inside a course (Properties > Course additional fields), it only stores a single static value. The Manage translations feature under Summary and languages only applies to the course Title, Short description, and Description, which is why switching from Norwegian to English UK there does not carry over.

In multilingual organizations I've worked with, the pattern that holds up best depends on what kind of data you are trying to display:

  • If the values are recurring or standardized (like audience, difficulty level, or category): Switch from a Text field to a Dropdown additional field. Because you can translate each dropdown option when configuring the field, learners will automatically see the selected value in their profile language.

  • If it is course-specific text that learners need to read in their own language: Move that content into the Course Description (or Short Description) under Properties > Summary and languages. That area natively supports multi-language translations (both manual and AI-assisted) and dynamically matches the learner's profile language.

  • If it is a brief, unique value that must stay in a text field: The only native fallback is formatting both languages in the same string (e.g., Norwegian / English), though this only scales cleanly if you support two languages.

You can check the full breakdown of how these two areas behave in the Docebo Help Center: