> 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/automation-permissions-how-to-assign-and-use.md).
# Automation Permissions: How to Assign and Use
Automation permissions allow team members to **create, manage, and execute automated workflows** for different platforms and channels. By assigning this permission, users can streamline repetitive tasks, saving time and ensuring consistent responses.
***
#### **Steps to Assign Automation Permission:**
1. Navigate to **Settings** from the left sidebar.
2. Click on **Teams**.
3. Select **Add User** or choose an existing user to configure permissions.
4. Click on **Configure Permissions**.
5. In the permissions window, go to the **Instance Permissions** tab.
6. Locate the **Automation** section.
7. Enable or disable specific permissions based on the level of access you want to provide.
***
#### **Permission Types**
Automation permissions are divided into types to control **what level of access a team member has over automation workflows**.
**1. View Automation**
* Allows team members to see existing automation workflows without making any changes.
* **Example:** A team lead wants to review automated messages sent to customers but should not modify them. Assigning **View Automation** ensures oversight without the risk of accidental edits.
**2. Manage Automation**
* Grants team members the ability to **create, edit, and delete automation workflows**.
* **Example:** A marketing team member needs to set up an automated welcome message for new users across WhatsApp and SMS. Granting **Manage Automation** lets them configure and deploy this workflow independently.
---
# 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/automation-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.