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

# User vault

Store private, user-specific entries in the Remote Desktop Manager user vault and access its credentials through user vault search or user-specific settings.

The ***user vault*** is a user-centric vault for entries of any type. It allows each user to create entries that only them can access.

{% hint style="info" %}
The user vault is available for all [advanced workspaces](/rdm/getting-started/workspaces/workspace-types/native-workspaces.md).
{% endhint %}

#### A note on credentials

Credentials in the user vault can be used in two ways:

* From a session using the ***user vault search***.
* When using the ***User-specific settings*** feature.

These restrictions can easily be understood when you keep in mind that the user vault is in fact contained in the user area of the database. It must be used from within the user vault, or by using our extension mechanism that is user specific.


---

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