> 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/administration/queue-and-ivr-access-control.md).
# Queue and IVR Access Control
This feature allows an admin to customize the access each user has to view, edit, create, and delete queues and IVRs, and to apply that access specifically to each queue or IVR. To set up queue and IVR access control, follow the steps below:
#### Create and Assign a Role
1. Navigate to Administration | Roles. Create or edit an existing [role](/administration/roles.md) and add the appropriate permissions for IVR and Queue. See screenshot below:
2. Navigate to Configuration | Users | Edit user | Roles Tab. Assign the role to the user(s) that need access to the queues and IVRs page.
#### Create and Assign a Data Access Policy
1. Navigate to Administration | Data Access Policies. Create or edit a [data access policy](/administration/data-roles.md) and add the appropriate access permissions for IVRs and Queues. See screenshot below:
2. Navigate to Administration | Organization Units | Select the appropriate queue or IVR object or organization unit that you would like to give access | Select Add member | Select the user(s) | Select the data access policy configured in step 3. | save.
3. The user(s) should now be able to see and access only the queues and IVRs that match their data access policy permissions.
{% hint style="info" %}
If a user is granted a data access policy assigned to an OU, permissions are inherited to all objects in the OU.
{% endhint %}
{% hint style="info" %}
Create permissions are required to be assigned to an OU. This will allow the user to create a queue or IVR in this OU.
{% endhint %}
---
# 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/administration/queue-and-ivr-access-control.md?ask=&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.
