> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/crm-v2/team-member/create-role-and-permissions-for-team-members.md).

# Create Role And Permissions For Team Members ?

### <mark style="color:red;background-color:orange;">Creating User Roles</mark>

1. Navigate to **Workspace settings > Roles and permissions > Add new user role**.
2. Name the role (e.g., "Manager") and grant access to various subsections:

   * WABA
   * WhatsApp API
   * CRM
   * Live Chat

   **Note:** By default, chat operators only see chats assigned to them.

   * To **hide customer mobile numbers** and identifiers, ensure the "Identifier" permission is not given.
   * To **automatically add the chat operator's name** to messages, enable the "Send chat operator name" option.

   For a **Manager** role, consider granting access to:

   * All contacts
   * Unassigned chats
   * New chats
   * All chats (assigned and unassigned)

   Additionally you can provide access to Automations Builder, Bot Builder and E-commerce *(based on specific requirements)*
3. Click **Save** to apply the role permissions.

{% embed url="<https://youtu.be/9wI1O4VbnCM?si=v4NEMqmU3njJN9JA>" %}


---

# 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://helpdocumentation.gitbook.io/user/crm-v2/team-member/create-role-and-permissions-for-team-members.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.