I think you need to look at your user provisioning options but not sure that your SSO tool can work with logic unless you code something that says only certain users be placed in that branch...Do you have an IT team that can help you with this? You may to write some scripts, etc.

I appreciate it! This is helpful!!

Unfortunately, may take a while for our IT team to be able to assist.

In the meantime - is it possible to assign everyone to a branch when they enroll, regardless if SSO or not? We’re just looking to place every single person in a branch when they log in. It would all be the same branch.

Ideally, we could allow someone to enter in an Additional User Field that would allocate them to a branch (they could select the branch upon sign up). But if that’s not possible, just assigning everyone to something other than the Root branch as an automation would be amazing if you know if that’s possible?

yes, you can do that through the automation app when using the CSV import option. There is a setting (we use when the branch is not identified in the CSV file). Note that this would apply to all users in your import file.

In the automation app, when confusing the import details, you will see a spot where you can define the default branch - see below

you can also create new branches if needed 

Thank you for this! Unfortunately we don’t use the CSV import option at this time… is there a way to do this with people just signing up? Like using Additional User Fields? Or just putting everybody in the same branch immediately?

I would be open to any method of doing this, even if it’s “convoluted” (like put everyone in a group which has an automation that puts them in a branch, etc.

Or is the only method available via CSV at this time?

Thank you again for your help!!

Sorry you said above that you are using the Automation App...is that not the case?

The screen shots are from the automation app set-up. Regardless of whether your entire process is automated, the import stems from a file so you should be able to set this up if you are indeed using the automation app to load your users.

So sorry, I didn’t mean to cause confusion here! I was using the automation app because I thought it was the best place to try to make this automatic - we don’t use the automation app for loading, I just hoped there was an option in Automation to make some kind of “When user is created”.

Honestly, this could be done anywhere. I was testing with the Advanced Settings > Self Registration option under “Registration Code Usage” but I can’t get the prompt to appear at all (guessing it’s because it’s SSO and not a normal registration?)

I could make it a manually added Additional User Field, but is there some kind of function that could say “if user has X in this Additional User Field, place them in Y branch” or some such? My goal is to just make it so when an SSO user signs up, they are either automatically placed into a specific branch, OR they can choose what branch they’d like to do (via Branch name, entering a code, anything).

Again, sorry for the confusion!

No worries just wanted to make sure I was giving you correct information.

Yes you can do that anywhere as you...I assume that those using SSO are your employee or are you using another authentication method like Linked In?

If they are your employees, your IT team could help with the coding to have all new users assigned to a designated branch but you may still need to move them. When we build connectors to handle user providing we usually add the branch fields and feed that from an HRIS. How you translate your org hierarchy to Docebo branch is what requires logic to built in as there is no built login in Docebo to do that. Hope this makes sense.

This makes great sense. Thank you ​@lrnlab !

For anyone reading this thread, I was actually able to achieve what I was struggling with without having to automate branch assignment. Just want to type it out in case someone wants to use it.

Basically, my company only uses SSO automatic user provisioning with very limited data. Suddenly, we wanted a way for someone not using our company email to access a custom made page we made. But there were two problems:

• We funnel everyone into the Root branch
• We have tons of required Additional User Fields we ask for that are employee-specific

Here’s how we solved the problem:

• All users outside must be hand-created by our team and are placed in a sub-branch
• We created an automatic group that contains every single employee with an employee email (used the domain name as a rule set)
• We reassigned all catalogs to this automatic group instead of the Root folder

Now, we have separation! Not ideal, but it works.

Thank you again ​@lrnlab for helping me troubleshoot!