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

# Set Up Organization Units

Navigate to Administration | Organization Units

When a queue or IVR is created, an object with the same name is automatically created in organization units. These objects can be move to another OU by using the drag and drop method.

Additional root units can be created by selecting the Add root unit button

Sub-units can be created by right clicking a root unit or another sub-unit.

Each OU or queue can be assigned a [Call Settings Policy](/administration/call-settings-policies.md) (settings for calls) and members (users) with data access policies. [Data access policies](/administration/data-roles.md) determine what data a user can access.

If a user has permission to access data at a higher level in the organization tree, these permissions are inherited to lower OUs and queues.

For more details see: [Organizational Units](/administration/organizational-units.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://cc.docs.landis.cloud/setup/setup-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.