> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/organizational-units.md).

# Organizational units

On the right-hand side of the **Organization Management → Overview** page, **Organization structure** shows your organization as a tree, with your top-level organization at the top and any organizational units nested underneath. Click a unit to expand or collapse it.

## Creating an organizational unit

{% stepper %}
{% step %}

#### Open the Overview page

Go to **Organization Management → Overview**.
{% endstep %}

{% step %}

#### Check which organization you're in

The new unit is created **under the organization you're currently switched into**, shown in the organization switcher at the top of the page. To add a unit under a different one, switch to it first.
{% endstep %}

{% step %}

#### Start a new unit

Click **Add organizational unit** (top right of the Organization structure panel), or the **Add organizational unit to&#x20;*****\<name>*** node inside the tree — it sits under the organization you're working in.
{% endstep %}

{% step %}

#### Name the unit

Give the unit a name — for example *Game Studio* or *Infrastructure Team*.
{% endstep %}

{% step %}

#### Create it

Click **Create organizational unit**. The dialog names the parent before you commit — *"Organizational units created here are added under **\<name>**"* — and the confirmation repeats it.
{% endstep %}
{% endstepper %}

The unit appears in the tree straight away, and in the organization switcher and the [Servers page](/organizations/servers-page.md) organization filter.

{% hint style="info" %}
**The switcher decides where a unit lands.** If you're switched into your top-level organization, the new unit sits directly beneath it. If you're switched into *Studio A*, it becomes a unit inside *Studio A*. Read the parent name in the dialog before creating — it's the quickest way to confirm you're in the right place.
{% endhint %}

## Good to know

* Only admins can create organizational units. If you aren't an admin, you'll see the structure but not the button.
* You'll have full administrative control over any unit you create, including inviting members within its scope.
* Names are up to 50 characters and must start with a letter or number.
* By default a structure can be up to **ten levels deep** and have up to **twenty units under any single parent**. If your company needs more, raise a support case and we'll increase it for you.
* A unit has exactly one parent — it can't sit in two places at once.

## What an organizational unit gives you

* **Scoped visibility.** Switch to a unit and you see only that unit's servers and members.
* **Centralized control.** From your top-level organization you can still see everything, across every unit beneath it.

{% hint style="info" %}
**Coming soon.** Two things the portal names as planned rather than available today: **role-based access for secure delegation**, and **shared billing and resource management** across an organization. Until then, see the note on [billing](/organizations.md) for how invoicing works.
{% endhint %}

## Related topics

* [Inviting a member](/organizations/inviting-a-member.md)
* [Importing an organization](/organizations/importing-an-organization.md)
* [The Servers page](/organizations/servers-page.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.i3d.net/organizations/organizational-units.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.