> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/knowledge-base/how-to-articles/assign-roles-and-permissions.md).

# Assign roles and permissions

Assign roles and permissions in Devolutions Cloud at the entry, folder, vault, or global level to control exactly what each user can access.

Roles and permissions can be assigned in Devolutions Cloud for each level by following a few simple steps.

To edit roles and permissions within a specific entry or folder, click on the ellipsis button next an entry name.

Alternatively, admins can go to ***Administration*** – ***Vaults***, and click on the ***Edit*** icon next to the vault to modify.

Regardless of the path chosen, the same ***Vault*** window should appear. Select the ***Security*** section and click the ***Edit*** tab to manage roles and permissions.

#### Global roles and permissions

To edit global roles and permissions, go to the ***Administration*** section located under ***System*** in the sidebar, then click on ***System Permissions***.

Then click on the ***Edit*** icon.


---

# 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://docs.devolutions.net/cloud/knowledge-base/how-to-articles/assign-roles-and-permissions.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.