> 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/concepts/advanced-concepts/permissions-rbac-and-roles.md).

# Permissions, RBAC, and roles

Control access in Devolutions Cloud with roles and RBAC that govern viewing, editing, and managing entries and vaults.

Permissions, RBAC, and roles describe how Devolutions Cloud controls who can see, use, or manage entries, vaults, and administrative settings. System and vault roles bundle permissions such as View sensitive, View password, Edit, or Manage permissions, letting administrators grant the minimum rights required to perform a job. Hidden fields and passwords always respect these permissions.

In Devolutions Cloud, roles are typically assigned through user groups and then applied at system or vault level, often combined with approval workflows and detailed reports. For example, Operators might be allowed to launch sessions without revealing passwords, while Managers can also edit entries and delegate access.

#### Related topics

* [Roles and permissions](/cloud/web-interface/administration/configuration-and-security/system-permissions/roles-and-permissions.md)
* [System permissions](/cloud/web-interface/administration/configuration-and-security/system-permissions.md)
* [Create and manage user groups](/cloud/web-interface/administration/management/user-groups/create-and-manage-user-groups.md)


---

# 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/concepts/advanced-concepts/permissions-rbac-and-roles.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.