HI @mcquills yes you can…

You will need to trace all new branches back to the parent branch AND use the branch codes as well. You will need to use this format to create the branches during your import:

Branch Name: Parent branch name/sub branch 1 name/sub branch 2 name/… and so on

Branch code: PARENT BR CODE/SUB 1 CODE/SUB 2 CODE/...and so on.

Note that you can only do this while creating new users or updating exiting users and you are essentially using the user import tool to create these + make sure to check the box that says “Create branches” when importing.

Think I have all the steps...if you run into any issues, let me know.

this is option to check when importing:

Must each branch also have an active user?

No, but if you want to generate the branch using the import method, there needs to be a user to create it. 

You could in theory make 1 fake user for each branch in you CSV, let all the branches be generated, and then delete all those test users (Give them a common name, username or attribute so you can search, select all and delete easily after).

@mcquills   Correct, you need to have at least 1 user (per branch) in your file since you are essentially creating a user and the ability to create a new branch is part of that process.

Something else to think about since I know you are looking into doing some fancier self-registration stuff, is you could have all your districts/schools created in your form, and then on the API calls from the selection, you could easily create the branches if they did not exist yet.

@lrnlab How do you map the Branch Name Path and Branch Code Path? I am checking the box to create new branches in the General Import Options. However, it still isn’t working for me. Test users are getting created without any branches. I have tried this option:

and this option:

Is the level supposed to be “User” or the number for the branch hierarchy?

Hi @mmarshall when creating branches during your user imports, you need to define the “branch name path” and “branch code path” from the root folder and write it like this:

Branch Name Path:

Root folder/Folder 1/Folder 2/etc. - all the way to the NEW branch you want to create.

Branch Code Path:

Do the same for the CODE - you MUST include both the name and the code for this work

Root folder code/Folder 1 Code/Folder 2 Code/etc.

NOTE: you also need to tell Docebo to create new branches when one is not found. This setting on on the user import panel + I highly recommend you define a “destination fallback branch” as a safety measure in case you wrote on branch name or code incorrectly; this option will place any users in that  branch if there its an issue with the import or if they have no branch defined in your file. I created a separate branch called “No Branch” to capture anyone who was not properly align to their branch and correct them manually.