> 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/server/knowledge-base/knowledge-base-articles/permission-sets.md).

# Permission sets

Manage permission sets in Devolutions Server using the default regular and PAM sets or by creating custom sets for specific needs.

Permissions can be grouped in ***Permission sets***. It is possible to create custom sets manually or use the default sets. They are managed via the Devolutions Server web interface in ***Administration*** – ***System settings*** – ***Vault management*** – ***Permission sets***.

## Default permission sets

Ten permission sets are created by default: three regular sets and seven PAM sets. They appear in the same table, with ***(Default)*** after their name and a ***PAM*** prefix for the PAM sets. Default permission sets cannot be edited or deleted.

### Regular permission sets

* ***Contributor***: Includes all permissions except the PAM permissions.
* ***Operator***: Includes the ***Connect (execute)***, ***View***, and ***View sensitive information*** permissions.
* ***Reader***: Includes the ***View*** and ***View sensitive information*** permissions.

### PAM permission sets

* ***Approver***: Includes the ***Approve checkout request***, ***Read logs***, and ***View*** permissions.
* ***Contributor***: Includes all permissions of the ***General***, ***Security***, ***Attachments***, and ***Documentation*** categories, as well as the ***Checkout***, ***Read logs***, and ***Reset password*** permissions.
* ***Log reader***: Includes the ***Read logs*** and ***View*** permissions.
* ***Manager***: Includes all permissions of the ***General***, ***Security***, ***Attachments***, ***Documentation***, and ***PAM*** categories.
* ***Operator***: Includes the ***Connect (execute)***, ***View***, ***View password***, ***View sensitive information***, ***Password history***, ***View attachments***, ***View documentation***, ***Checkout***, and ***Read logs*** permissions.
* ***Owner***: Includes all permissions of the ***General***, ***Security***, ***Attachments***, ***Documentation***, and ***PAM*** categories.
* ***Reader***: Includes the ***Connect (execute)***, ***View***, ***View attachments***, ***View documentation***, ***Checkout***, and ***Read logs*** permissions.

## Custom permission sets

Create a new set that suits your specific needs:

1. In ***Administration*** – ***System settings*** – ***Vault management*** – ***Permission sets***, click ***Add permission set***.
2. Enter a ***Name*** for the custom set.
3. Select a permission category in the list on the left: ***General***, ***Security***, ***Attachments***, ***Documentation***, ***More***, or ***PAM***.
4. Check each permission to include in the set, or check ***Select all*** to include every permission of the category.
5. Repeat the category selection for each category that contains permissions to include.
6. Click ***Save***.
7. Save the changes to the ***Vault management*** settings.

The custom permission set appears alongside the default ones in the table. Use the ***Edit*** and ***Delete*** buttons on its row to modify or remove it.

{% hint style="info" %}
See [Batch grant access](https://docs.devolutions.net/server/knowledge-base/knowledge-base-articles/batch-grant-access.md) to learn how to grant permission sets to multiple users, user groups, and application users at once.
{% endhint %}

#### See also

* [Devolutions Blog - Decoding permission sets and privilege sets](https://blog.devolutions.net/2025/02/decoding-permission-sets-and-privilege-sets/)
* [Devolutions Academy – Configuring entry permissions and inheritance](https://academy.devolutions.net/student/page/2942425-configuring-entry-permissions-and-inheritance?curriculum_activity_id=4493533\&path_id=2942210\&sid=a388a775-35a7-40e0-b037-82fd7f00e34c\&sid_i=0)


---

# 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/server/knowledge-base/knowledge-base-articles/permission-sets.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.
