> 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/cloud/web-interface/vault-access-in-devolutions-cloud/approve-vault-access-in-devolutions-cloud.md).

# Approve vault access in Devolutions Cloud

Approve or deny public vault access requests in Devolutions Cloud from the Dashboard and set the permission level granted to users.

In Devolutions Cloud, users can request access to a public vault. An administrator / vault owner then has to approve the request. Vault owners are configured in ***Administration – Management – Vaults*** when creating or editing a vault, under the ***Visibility*** option.

### View pending vault access requests

To accept the pending requests, click on a specific entry in the ***Pending vault Access Requests*** section, which is in the ***Dashboard***. This will open the ***Approval request*** window which is described in the next section.

{% hint style="info" %}
Pending requests will only show up in the ***Dashboard*** if you are in a vault that a user has requested access to.
{% endhint %}

### 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 accept pending requests, use the ***Pending vault Access Requests*** section in your ***Dashboard***. Clicking on the request will open the ***Approval request*** window.

This view is divided into two sections:

* The ***For*** 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 ***Awaiting approval*** section allows you to write a message to the user explaining your decision, but it remains optional.

{% hint style="info" %}
The ***Permissions*** level set by the user making the request can by modified by the approver. You can read more on [Roles and permissions](/cloud/web-interface/administration/configuration-and-security/system-permissions/roles-and-permissions.md).
{% endhint %}

Clicking on ***Approve*** or ***Deny*** will send the response with the selected parameters.

{% hint style="info" %}
To learn more about the end user experience in Devolutions Cloud, visit [Request vault access in Devolutions Cloud](/cloud/web-interface/vault-access-in-devolutions-cloud/request-vault-access-in-devolutions-cloud.md).
{% 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 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/cloud/web-interface/vault-access-in-devolutions-cloud/approve-vault-access-in-devolutions-cloud.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.