Please note that only Administrators can enable ADUs, but users must have an HR manager role to be able to have the ADU Admin role
How to enable ADU’s?
Administrators have access to enable the ADUs from the ADU page found under System config > Divisions/ADU'S
When you click onto ADUs, you will see the following screen where you will be able to enable ADUs
When ADUs are first enabled, all Teams and Users will reside in the root division (ADU). A user with the ADU Admin role can then create sub-divisions and move Teams and Users to them, thereby segmenting the data into separate divisions.
To enable ADUs, you must grant at least 1 the ADU Admin role. This role provides access to the Divisional Data Transfer Tool, and grants access to data across all divisions as well as making changes to the division structure. Please refer to this article, to find steps on how to assign a user with an ADU Admin role.
In addition to this, you must also confirm the name of the root ADU, by default it will display the Domain name as the Root ADU, but you have the ability to change this.
ADU’s can be managed and configured within System Config > Divisions/ADUs or from the Organization page
Creating Divisions (ADUs)
Divisions can only be created by users with the ADU Admin role.
This can be done from the Organization page, which is under Org Admin > Organization as shown in the screenshot below:
To create a new Division (ADU), click the + icon, when you click this icon you will see a dialog box which will allow you to define the Division name and decide what the parent division should be
If you no longer wish to use ADUs, then you are able to disable this within Configuration > ADU page.
By disabling ADU’s, you will be making the following changes:
- You will be deleting all ADU structures
- All data will now be accessible by any user with the HR Manager role regardless of current ADU.
- All ADU Admin roles will be revoked
Please note that this process cannot be undone.