> 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/web-interface/vault-access-in-devolutions-server/approve-vault-access-in-devolutions-server.md).
# Approve vault access in Devolutions Server
In Devolutions Server, users can request access to a public vault. An administrator / vault owner then has to approve the request. Vault owners are configured in ***Administration – Security Management – Vaults*** when creating or editing a vault, under the ***vault owners*** section.
### View pending vault access requests
To view the number of pending requests, you can look at the following ***Pending vault Access Requests*** box in the top of the ***Dashboard***. To accept the pending requests, scroll down to the ***Pending vault Access Requests*** section. Using the ***Messages*** button, you can view the ***Vault Access Request*** message of a specific request.
{% hint style="info" %}
If there is a vault owner for the requested vault, the administrator will not receive a ***Message***.
{% endhint %}
Finally, clicking on the ***Approve*** and ***Deny*** buttons opens the ***Vault Access Request Response*** window, which is described next.
### Approve/Deny vault access requests
{% hint style="info" %}
Depending on the workspace, administrators / vault owners may receive an email informing them of the vault access request:
* With a Devolutions Cloud workspace, a vault access request email is sent to the administrator / vault owner to whom the request has been addressed.
* With a Devolutions Server workspace, all administrators / vault owners receive a vault access request email.
* With an SQL workspace, no email is sent.
{% endhint %}
To respond to a request, you can use the ***Pending vault Access Requests*** box or open the ***Vault Access Request Response*** window.
The first option is to use the ***Pending vault Access Requests*** section (see image below) in your ***Dashboard***, it can be found by scrolling down. Clicking on either the green check mark (approve the request) or the red "X" (deny the request) next to a request will open the ***Vault Access Request Response*** window.
The second option requires you to go through the other ***Messages***. Whatever way you choose to access the response window, the result will be the same.
This view is divided into two sections:
* The ***Request Info*** section contains information about the user's request. Because this was done on the user's side, fields in this section cannot be edited.
* The ***Response Parameters*** section allows you to write a message to the user explaining your decision, but it remains optional.
The button to send the response (***Approve request*** or ***Deny request***) will change, depending on what you selected earlier.
{% hint style="info" %}
To learn more about the end user experience in Devolutions Server, visit [Request vault access in Devolutions Server](https://docs.devolutions.net/server/web-interface/vault-access/request-vault-access).
{% endhint %}
---
# 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:
```
GET https://docs.devolutions.net/server/web-interface/vault-access-in-devolutions-server/approve-vault-access-in-devolutions-server.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
