Best Practices

Best Practices

• If you plan to manage the org chart via an integration (for example Salesforce), API call, or a CSV import then it is recommended to always use a CODE value that is unique. This would disambiguate the specific branch during the import process. Having the same code as an existing item may cause internal conflicts that the system cannot process on its own, resulting in errors during the import.
• Since a user can be moved from a branch to another, only manually and via API or CSV, please consider that a very nested branch structure might be hard to be kept updated, especially if your users move from a branch to another very often. Prepare your branching structure considering how you would like to deliver the learning content (by BU, by role, by region...), rather than replicating the company hierarchy structure. If there are continuous changes in your company's organizational chart, try to keep the branches at a higher level and work with automatic groups through additional fields, that can be updated by you as the Superadmin or by the users themselves.
• Try to avoid using the root branch (level 0) as much as possible, as it behaves differently than all the other branches (e.g. you won't be able to display the users that are ONLY in the root branch: the system will always display users from all the organization chart tree in this case). Users should always be placed in a branch structure underneath the root, this will help to filter when selecting users for reporting and enrollments.
• Try to avoid placing a user in multiple branches, as if often can make user management and user experience more complex (i.e. it may trigger multiple notifications for them). Rather than placing a user into two or more branches, you can place the user in a single branch, then place them in different groups.