> 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/rdm/da/user-interface/navigation-pane/user-vault.md).

# Brugerboks

Gem private, brugerspecifikke poster i brugerboksen i Remote Desktop Manager, og få adgang til dens legitimationsoplysninger via søgning i brugerboks eller brugerspecifikke indstillinger.

***Brugerboksen*** er en brugercentreret boks til poster af enhver type. Den giver hver bruger mulighed for at oprette poster, som kun brugeren selv kan få adgang til.

{% hint style="info" %}
Brugerboksen er tilgængelig for alle [avancerede arbejdsområder](/rdm/da/getting-started/workspaces/workspace-types/native-workspaces.md).
{% endhint %}

#### En bemærkning om legitimationsoplysninger

Legitimationsoplysninger i brugerboksen kan bruges på to måder:

* Fra en session ved hjælp af ***søgning i brugerboks***.
* Når funktionen ***Brugerspecifikke indstillinger*** bruges.

Disse begrænsninger er lette at forstå, når De husker, at brugerboksen faktisk ligger i brugerområdet i databasen. Den skal bruges inde fra brugerboksen eller ved hjælp af vores udvidelsesmekanisme, der er brugerspecifik.


---

# 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/rdm/da/user-interface/navigation-pane/user-vault.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.