# Organizational Units (OUs)

### Scope <a href="#scope" id="scope"></a>

This document explains how **Custom Organizational Units (Org Units)** are used to define and manage a hierarchical organizational structure within a Business Organization.

Org Units are optional and intended for **administrative organization, policy application, and delegation**, not direct permission control.

***

### I am new. Where should I start? <a href="#i-am-new.-where-should-i-start" id="i-am-new.-where-should-i-start"></a>

If you are new to Organizational Units:

* Start with the **default root Org Unit**
* Only create additional Org Units if your organization has multiple departments, teams, or business functions
* Use Org Units to structure users and policies, not to replace roles

Small organizations may not need Org Units at all.

***

#### Purpose <a href="#purpose" id="purpose"></a>

Organizational Units help organizations:

* Model real-world hierarchies\
  \&#xNAN;*(for example: Company → Department → Team)*
* Group users logically without relying only on roles
* Apply security policies at different organizational levels
* Delegate administrative responsibilities more granularly

***

#### When should I use Organizational Units? <a href="#when-should-i-use-organizational-units" id="when-should-i-use-organizational-units"></a>

Organizational Units are useful when:

* Your organization has multiple departments or teams
* Different groups require different security or access policies
* Administrative control needs to be separated by business function
* You want policy inheritance based on organizational structure

> **Note**\
> Using Organizational Units is optional.\
> Small or simple organizations may operate effectively without them.

***

#### Prerequisites <a href="#prerequisites" id="prerequisites"></a>

Before creating Organizational Units, ensure that:

* You have administrative access to the organization
* You understand your organization’s internal structure
* A root or parent Organizational Unit already exists

***

### I already understand. How do I proceed step by step? <a href="#i-already-understand.-how-do-i-proceed-step-by-step" id="i-already-understand.-how-do-i-proceed-step-by-step"></a>

***

#### 1. Open Organizational Units <a href="#id-1.-open-organizational-units" id="id-1.-open-organizational-units"></a>

* Sign in to the [Admin Console](https://admin.oten.live/).
* Navigate to [Organizational Units.](https://admin.oten.live/organizational-units)\
  \
  ![](/files/Golq66vSHxVpQ4sqd5Ld)

***

#### 2. Create a New Organizational Unit <a href="#id-2.-create-a-new-organizational-unit" id="id-2.-create-a-new-organizational-unit"></a>

* Click **Create Org Unit**\
  \
  ![](/files/TcE5ZdU3sWM0iCDd7fc9)
* Enter an **Org Unit name** (required)
* Optionally, enter a **Description** to explain the unit’s purpose
* Select a **Parent Organizational Unit**\
  ![](/files/d4NPzhaHlE6bUX1pkLdm)<br>

**UI highlight:**

* Org Unit name field
* Parent Org Unit selector

***

#### 3. Define the Parent–Child Relationship <a href="#id-3.-define-the-parent-child-relationship" id="id-3.-define-the-parent-child-relationship"></a>

* In the **Select Parent Org Unit** section, search for an existing unit
* Select the appropriate parent to define the hierarchy
* Confirm the selection\
  \
  ![](/files/FepCzl10h4nDX4yv8e1S)

> **Note**\
> Every Organizational Unit must have a parent, except the root unit.

***

#### 4. Create the Organizational Unit <a href="#id-4.-create-the-organizational-unit" id="id-4.-create-the-organizational-unit"></a>

* Review the Org Unit name, description, and parent
* Click **Create Org Unit** to save

![](/files/t2hGnKLpVWIbMCsUVZYY)<br>

After creation:

* The Org Unit appears in the organizational hierarchy
* Inherited policies are applied automatically\
  ![](/files/fXoXJMBiXlH5YguROhyy)

***

#### 5. Manage Users and Policies (Optional) <a href="#id-5.-manage-users-and-policies-optional" id="id-5.-manage-users-and-policies-optional"></a>

After creating an Organizational Unit, administrators can:

* Assign users to the Org Unit
* Apply security policies at the Org Unit level
* Delegate administrative roles scoped to that Org Unit


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://oten.gitbook.io/identity-support/user-guide/business-account/business-owner-default-authority/organizational-structure/organizational-units-ous.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
