> 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/password-manager/knowledge-base/application-knowledge-base/approve-vault-access.md).

# Approve vault access

Approve or deny public vault access requests in Devolutions Password Manager by reviewing details and setting the access duration from the Messages panel.

In Devolutions Server, users can [request access to a public vault](https://docs.devolutions.net/server/web-interface/vault-access-in-devolutions-server/request-vault-access-in-devolutions-server). An administrator or vault owner can approve the request via Devolutions Password Manager.

### View pending vault access requests

***Vault Access Requests*** can be viewed using the ***Messages*** button. On Windows and macOS, ***temporary access requests*** are also listed there.

{% hint style="info" %}
If there is a vault owner for the requested vault, the administrator will not receive a ***Message***.
{% endhint %}

### Approve/Deny vault access requests

The message box displays information about the request. Click on the ***eye*** to view the details of the request.

This view is divided into two sections:

* The ***Request Info*** section contains information about the user's request.
* The ***Response Parameters*** section allows you to change the ***access duration*** and to write a ***message*** to the user explaining your decision (optional). Finally, you can ***Approve*** or ***Deny*** the request.


---

# 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/password-manager/knowledge-base/application-knowledge-base/approve-vault-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.