# Organizational units

You define the hierarchy for your organizational units (OUs) with the `organziationalUnits` property at the top level of the organization.yml file. It's an object whose keys are OU paths, and values are configuration for the corresponding OUs.

The root OU of the hierarchy is always **Root**, and all other OUs are its children.

#### Examples

This is the minimum hierarchy. As you can see, you must have the Root OU but you don't have to provide configuration for it.

{% code title="organization/organization.yml" %}

```yaml
masterAccountId: "098765432100"

organizationalUnits:
  Root: {}
```

{% endcode %}

Here we have a more complex hierarchy with some nested OUs.

{% code title="organization/organization.yml" %}

```yaml
masterAccountId: "098765432100"

organizationalUnits:
  Root/Workloads/Dev: {}
  Root/Workloads/Test: {}
  Root/Workloads/Prod: {}
  Root/Sandbox: {}
```

{% endcode %}

The above configuration is flat but represents this kind of hierarchy:

```bash
Root
├─ Workloads
│  ├─ Dev
│  ├─ Test
│  └─ Prod
└─ Sandbox
```


---

# 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://organizations.takomo.io/organization-configuration/organizational-units.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.