> 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/knowledge-base/how-to-articles/set-up-user-vault-credentials-in-remote-desktop-manager.md).

# Set up user vault credentials in Remote Desktop Manager

Apply user vault credentials to an entry in Remote Desktop Manager using a user-specific setting without affecting other users.

You can configure an entry to apply credentials that are in your user vault without affecting other users' settings. To do so, you need to create a ***User-specific setting***. Follow the steps below.

1. Select the entry in the ***navigation pane***, then go to ***Edit – User-specific settings***.
2. In the ***General*** tab, enable ***Override credentials***.
3. In the drop-down list next to this option, select ***Linked (user vault)***.
4. Select your credentials or, alternatively, select ***Prompt on connection*** to receive a list of credential entries when you connect to the session entry.
5. Click ***OK*** to save your changes.

You will now be prompted for the credentials you selected to open the entry.


---

# 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/knowledge-base/how-to-articles/set-up-user-vault-credentials-in-remote-desktop-manager.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.