Automatic Branch Assignment

@rgraf There are several approaches you might take, but they are related to registration.

If your company uses SSO to authenticate, you can use an additional field to assign that branch. This is a bit complex so let me know if this is an approach you want more information about.

Another approach is to assign a branch code, and then require that branch code during self-registration. It’s in this area of the Advanced Settings. The KB will have more details.
 

You can also assign branch codes to your .csv files when you do a batch upload.

If you are looking to move users between branches, you can do that from User Management > Choose Actions.

Also if you use the CSV user import method or the Automation tool to load and maintain your users, you can set a default branch when you so this or you can add a Branch Name and Branch Code option to our import templates to place each user in their respective branch when their profiles are created...Depends on what processes you use, or plan to use...

​@KMallette I would love to know more about the SSO config.

We noticed this week that our new hires were no longer being mapped to branches as they had been before. I took over as admin of our instance of Docebo so I did not initially set up this field. If you could point me to any resources about how to check or update these parameters I would appreciate it.

What method do you use to import your users?

SAML SSO

​@ChrisBurton are you provisioning your users from your source app as with this process? If yes, that’s likely where you need to start checking what may have happened to your set-up. I haven't used provisioning with Docebo so far so unfortunately I cannot say whether that is the source of the issue or whether it’s on your Azure app (assume you use this as it’s the most popular)

I am not sure, I have a request out to our IT team to support in this area. I imagine they are pulling in from Azure but that is a guess.

If we assume it is Azure, is there a place to see inside of Docebo how the fields are being (or were being, or should be) mapped to branches? I know it was happening before but now everyone is going to the root branch.

A good idea…

I do see the branch fields in the provisioning block so you’d have to make sure you output source is aligned to these fields