Structuring OUs

Follow

A child OU can only have one parent OU, but a parent OU can have unlimited child OUs. If an OU has too many direct child OUs, it can become difficult to view them in the Organization Chart, but there is no limit to how deep your OU structure can go, so make use of those layers if you can.

Consider your organization's structure before you start creating OUs in the application. We typically recommend two approaches:

  • Use a single top-level OU to represent the company.
  • Use multiple top-level OUs to represent different business units or areas of work.

The structure you choose should be determined by how you manage funding at your company. You need at least one top-level OU per funding source, so if you have a single team that will be managing all of the funding for your organization, it makes sense to use a single top-level OU. If you have many different teams that manage their own funding sources, you will want a top-level OU for each of the funding sources so you can control the permissions on each funding source separately.

 

Was this article helpful?
0 out of 0 found this helpful