> 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 polices. [Data access polices](/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 dynamically by asking a question.

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

```
GET https://cc.docs.landis.cloud/setup/setup-organizational-units.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.