> 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/instance-permission/marketing-permissions-how-to-assign-and-use.md).

# Marketing Permissions: How to Assign and Use

Marketing permissions allow team members to access, manage, and execute marketing-related tasks such as segmenting contacts, running campaigns, and managing automated workflows. Assigning these permissions ensures that the right team members can handle marketing operations efficiently without compromising data security.

***

### Steps to Assign Marketing Permission:

1. Navigate to **Settings** from the left sidebar.
2. Click on **Teams**.
3. Select an existing user or click **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 **Instance Permissions** tab.
7. Locate the **Marketing** section.
8. Enable or disable specific permissions based on the level of access you want to provide.

<figure><img src="/files/0ld5LLzCpaANccdChNEc" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/instance-permission/marketing-permissions-how-to-assign-and-use.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.