> 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/simplifying-role-based-access-in-mercuri-use-cases-and-solutions.md).

# Simplifying Role-Based Access in Mercuri: Use Cases and Solutions

Mercuri allows businesses to manage user access with **fine-grained permissions**, giving you full control over who can view or take action across different parts of the platform. 

Whether you’re managing a small team or scaling across multiple locations, this flexibility ensures that the right people have access to the right tools.

### Use Case 1: Managing Access Across Multiple WhatsApp Numbers

{% embed url="<https://www.youtube.com/embed/HsptVgZOLoE?autoplay=1&loop=1&mute=HsptVgZOLoE1&playlist=>" %}
Quick demo to set up user permission
{% endembed %}

Let’s say your business uses **multiple WhatsApp numbers,** one for sales and another for support. Naturally, you want only the sales team to access the sales inbox, and support agents to access customer support chats.&#x20;

Granting full access to all inboxes would create confusion, potential data leaks, and miscommunication.

#### How to Assign Granular Permissions

To implement this setup:

1. **Go to**: `Settings > Teams`
2. **Click**: `Add User`
3. **Fill in** the new user's details (name, email, role, etc.)
4. Under the **Permissions** section:
   * Locate the **Conversations** dropdown
   * Select the specific **WhatsApp number** this user should access
   * Choose **“Assign Agent”** to allow them to manage chats for that number

You can repeat this process for each team member, ensuring clean access control for multi-channel operations.


---

# 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/simplifying-role-based-access-in-mercuri-use-cases-and-solutions.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.