> 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/request-vault-access-in-devolutions-server.md).

# Request vault access in Devolutions Server

Request access to an entire public vault in Devolutions Server by browsing all vaults, sending a request with an optional message, and awaiting approval.

You can request access to a public vault in Devolutions Server. Follow the steps below to complete a request.

1. Connect to the Devolutions Server that contains the vault you want access to.
2. In the vault selector drop-down menu, click ***More*** and then click on ***Browse All vaults***.
3. Choose the vault you want to access, then click on ***Request Access***.
4. Write a short message to the approver explaining why the access to this vault is needed. The message is optional, but we recommend it as it allows the administrator or vault owner to make a more informed decision.
5. Click on ***Send Access Request***.

You now have to wait for the approver to respond to your request. If they approve your request, the vault will appear in the vault selector drop-down menu with the other vaults you already have access to.

#### See also

* [Devolutions Academy – Manage vault access requests in Devolutions Server](https://academy.devolutions.net/student/activity/3567141)


---

# 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/web-interface/vault-access-in-devolutions-server/request-vault-access-in-devolutions-server.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.