> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/account/user-and-role-management/assigning-permissions.md).

# Assigning permissions

1. Go to the **Account → Users** tab. Select the user, click the **Edit** button, and then go to the **Permissions** tab.

<figure><img src="/files/DtCcpnc25EKPkV0PQ3xm" alt=""><figcaption></figcaption></figure>

2. In the **permissions section**, select the areas that the user will have access to. After making your selections, click **Save** to confirm the assigned permissions.

### **Types of permissions granted to users**

Below are the types of permissions you can grant to a user. If a drop-down icon (downward arrow) appears next to a permission, it means you can assign the permissions in even more specific areas.

### **Email** (Email Campaigns and Email API)

<figure><img src="/files/mVLUXqeTxgyUoBAzY4le" alt=""><figcaption></figcaption></figure>

### **SMS**

<figure><img src="/files/ngPMy3PTpJXaCBlLt1Zw" alt=""><figcaption></figcaption></figure>

### **Account**

<figure><img src="/files/HMX2h5yS2AlJFNcCOdAq" alt=""><figcaption></figcaption></figure>

### **Contacts**

<figure><img src="/files/WFxeBGjxElfqiwFoKByE" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
For **Email API**, it's necessary to define which SMTP sub-accounts will have specific permissions granted.
{% 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 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.messageflow.com/account/user-and-role-management/assigning-permissions.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.