> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/users-management/common-permissions/channel-permissions-how-to-assign-and-use.md).
# Channel Permissions: How to Assign and Use
Channel permissions allow team members to view or manage connected communication channels, such as **SMS** and **WhatsApp** within Mercuri CX. These permissions help control who can access, monitor, and modify channel configurations or onboard new numbers.
***
#### Steps to Assign Channel Permissions:
1. Navigate to **Settings** from the left sidebar.
2. Click on **Teams**.
3. Select an existing user or click on **Add User** to create a new one.
4. Enter the required details such as **Name**, **Email**, and **Role**.
5. Click on the **Configure Permissions** button.
6. In the permissions window, go to the **Common Permissions** tab.
7. Locate the **Channels** section.
8. Enable or disable specific permissions based on the level of access required.
***
#### Permission Types
**1. View Channels**
Allows team members to view existing SMS and WhatsApp channel configurations, including onboarded numbers, opt-in/out settings, and auto-responses.
**Example:**\
A team member who needs to check which numbers are active and review auto-response or opt-in/out messages without making any edits can be assigned the *View Channels* permission.
**2. Manage Channels**
Grants access to onboard new SMS or WhatsApp numbers, edit or remove existing numbers, and modify related configurations such as opt-in/out messages, auto-responses, and authentication details.
**Example:**\
A user responsible for maintaining communication setups can onboard new WhatsApp or SMS numbers, update opt-in/out messages, and configure auto-responses. Assigning *Manage Channels* gives them full control over these actions.
---
# 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://docs.mercuri.cx/features/users-management/common-permissions/channel-permissions-how-to-assign-and-use.md?ask=&goal=
```
`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.