> 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/batch-grant-access.md).

# Batch grant access

Use batch grant access in Devolutions Server to assign permissions and permission sets to multiple users, user groups, and application users at once.

The ***Batch grant access*** feature allows you to assign permissions and permission sets to multiple users, user groups, and/or application users at once on entries, folders, and vaults.

## Location

***Batch grant access*** can be found in the properties of entries, folders, and vaults under ***Security – Permissions***. Set the ***Permission*** to ***Custom***, then click ***Grant access***. The ***Grant access*** button is only available to users who can edit permissions.

It can also be accessed via ***Administration***:

1. In the Devolutions Server web interface, go to ***Administration – System settings – Vault management***.
2. Under ***Default permissions***, select ***Custom*** in the ***Permission*** drop-down menu.
3. Click ***Grant access***.

The ***Batch grant access*** window is now open.

The window is divided in two sections: the permission settings and the user selection.

## Settings

### Permissions

In the ***Permission*** drop-down menu, set how the permissions are applied to the selected users. When ***Custom*** or ***Custom + Inherited*** is selected, the ***Action*** drop-down menu specifies how the selected permissions affect the existing ones:

* ***Add to existing***: Adds the selected permissions to the existing permissions of the selected users.
* ***Replace all with***: Replaces the existing permissions of the selected users with the selected permissions.
* ***Find and remove these***: Removes the selected permissions from the existing permissions of the selected users.

In the ***Grant by*** drop-down menu, select how to choose the permissions:

* ***Permissions***: Check individual permissions. Click ***Toggle all*** to check or uncheck every permission.
* ***Permission set***: Select a default or custom set in the ***Permission sets*** drop-down menu.

The permission sets offered depend on where ***Batch grant access*** is opened:

* Entries: regular permission sets.
* PAM entries, folders, and vaults: regular and PAM permission sets.
* PAM accounts: PAM permission sets.
* ***Default permissions*** in ***Vault management***: regular and PAM permission sets.

{% hint style="info" %}
Permission sets are created and configured in ***Administration – System settings – Vault management – Permission sets***. For more information, see [Permission sets](https://docs.devolutions.net/server/knowledge-base/knowledge-base-articles/permission-sets.md).
{% endhint %}

### Users

Users can be selected one by one by checking the box next to each one, but this method can be tedious if you have a lot of users. Tools are available to help you in your selection process:

* ***Filter***: Filter through your users, user groups, and application users by ***Name*** or ***Description***.
* ***Type***: Display only the ***User***, ***User group***, or ***Application*** type. The ***Application*** type is available when application users exist.
* ***Selected***: Display only selected or unselected users, user groups, and application users.

Click ***Select*** to apply the permissions to the selected users.

#### 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/batch-grant-access.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.
