> 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.md).

# Bokse

Forstå bokse i Devolutions Cloud, herunder den delte standardboks og den personlige brugerboks, plus anbefalede grænser for poster.

***Bokse*** er beholdere til poster, legitimationsoplysninger, følsomme oplysninger, sessioner og mere.

De starter med to:

* Én primær ***standardboks***, der er oprettet til at dele poster med teammedlemmer, som De giver adgang. De kan tilføje og dele flere bokse under ***Administration – Bokse***.
* Én ***brugerboks***, som er brugercentreret og bruges til at gemme oplysninger som legitimationsoplysninger til personlige konti. ***Brugerboksen*** forhindrer brugere i at bruge et usikkert værktøj til at administrere personlige adgangskoder på arbejdet. ***Brugerboksen*** kan deaktiveres under ***Administration – Systemindstillinger***.

{% hint style="success" %}
Indlæsning af bokse med et stort antal poster (dvs. over 2000) kan give ydelsesproblemer, og det anbefales derfor at organisere poster på tværs af flere bokse. Der er ingen grænse for, hvor mange bokse der kan oprettes.
{% endhint %}

#### Se også

* [Devolutions Academy – Arbejde med Deres bokse](https://academy.devolutions.net/student/page/2640024-working-with-your-vaults?curriculum_activity_id=4269754\&path_id=2543918\&sid=9a068cf7-780c-4a2b-8f00-61f18d3f7325\&sid_i=0)


---

# 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.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.