> 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/knowledge-base-articles/find-by-name-user-vault-entry-credentials-option.md).

# Find by name (user vault) entry credentials option

Use the Find by name (user vault) credentials option in Remote Desktop Manager to link an entry to credentials stored in your user vault.

In Remote Desktop Manager, users can edit entries to retrieve credentials stored in a credential entry located in their user vault by using the ***Find by name (user vault)*** option.

To do so, simply right-click on an entry requiring credentials, such as an RDP session, and select ***Properties***.

In the ***General*** view, open the credentials dropdown menu, and choose ***Find by name (user vault)***, then enter the name of the entry from which you wish to retrieve your credentials in the adjacent field.

Update the entry to save your changes. The entry will now automatically use the credentials from the entry specified in the ***Find by name (user vault)*** field.

#### Related topics

* [Find by name (user vault) entry credentials option](/rdm/knowledge-base/knowledge-base-articles/find-by-name-user-vault-entry-credentials-option.md)


---

# 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/knowledge-base-articles/find-by-name-user-vault-entry-credentials-option.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.