Skip to main content
Answer

So confused - I thought in the past we could map a default language to a branch?

  • October 22, 2025
  • 2 replies
  • 42 views
dklinger
Hero III
Forum|alt.badge.img+11

I swear we could do this - I even advised that we could do this...but in 2025? I cant find anything recently pointing at the capability of mapping a branch to a default language (so when we map individuals - we map them to an appropriate experience 99% of the time).

What we have been doing is sending people along to a branch that has a somewhat mixed experience inadvertently. A task widget that was customized in English need to be customized in Spanish is where we need to go with this.

Lets say I know where to do the customization. But how do we map people appropriately to the correct preferred language based on the branch (for those slower on the uptake)?

 

 

Best answer by mstrom

Hi ​@dklinger hmm...I don’t recall seeing an option to edit a branch and define the default language in the past. I know you can set additional fields visibility by branch. Were you thinking of that? That still won’t set a default language to serve up the right content/visibility. How are you mapping your users that fall under this branch? Setting their preferred language as part of that user provisioning process would be the way to go IMO. Of course, you’ve got to setup the backend to recognize what their language is to serve up the right content and pages via menus, catalogs, groups, localization etc. I know you know that though! 🙂

2 replies

M
Novice III
Forum|alt.badge.img+1
  • mstrom
  • Answer
  • October 24, 2025

Hi ​@dklinger hmm...I don’t recall seeing an option to edit a branch and define the default language in the past. I know you can set additional fields visibility by branch. Were you thinking of that? That still won’t set a default language to serve up the right content/visibility. How are you mapping your users that fall under this branch? Setting their preferred language as part of that user provisioning process would be the way to go IMO. Of course, you’ve got to setup the backend to recognize what their language is to serve up the right content and pages via menus, catalogs, groups, localization etc. I know you know that though! 🙂

dklinger
Hero III
Forum|alt.badge.img+11
  • dklinger
  • Author
  • Hero III
  • October 24, 2025

Morning - I think I twisted something in what we were implementing.

I believe you can use preferred language to pin down a group (not the inverse). And you can use branches (to formulate a group) and provisioning (set a language) to deliver that initial experience.

Will be going to the white board to figure it out. And because we are using Docebo Connect for the provision? It should just come down to adding a field to the recipe, clean up the few hundred folks that do not have a preferred language set, and move it forward in a more productive way.

Terms & ConditionsCookie settingsAccessibility statement