> 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/da/web-interface/administration/management/vaults/restrict-vault-access.md).

# Begræns adgang til bokse

Begræns adgang til bokse i Devolutions Cloud ved at tildele rollen Begrænset, så brugere eller grupper kun ser tilladte mapper og poster.

Administratorer kan give brugere mulighed for at se bestemte mapper eller poster i en boks. ***Rollen Begrænset boks*** tildeles på boksniveau. Brugere eller grupper med denne indstilling ser kun det boksindhold, de har tilladelse til at se.

{% hint style="info" %}
Funktionen er også fuldt kompatibel med Remote Desktop Manager og Devolutions Password Manager (computer, mobil og browserudvidelse).
{% endhint %}

1. Vælg boksen, og klik på de tre prikker for at redigere boksens tilladelser.
2. Tildel den ønskede bruger eller gruppe rollen ***Begrænset***, og klik på ***Opdater***.
3. Giv brugere eller grupper den ønskede adgang i mappens egenskaber eller i poster ved at klikke på ***Rediger***.

Når det er gjort, ser de berørte brugere kun det, de har tilladelse til at få adgang til.


---

# 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/da/web-interface/administration/management/vaults/restrict-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.