> 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/es/knowledge-base/knowledge-base-articles/dynamic-credential-linking.md).

# Vinculación dinámica de credenciales

Utilice la vinculación dinámica de credenciales en Remote Desktop Manager para vincular una entrada de sesión a un conjunto específico de credenciales de una lista solicitada.

La vinculación dinámica de credenciales en Remote Desktop Manager se refiere a la acción de vincular una entrada de sesión con una entrada de credenciales que normalmente mostraría al usuario una lista (p. ej., ***Lista de contraseñas*** o ***LastPass*** con la opción ***Preguntar siempre con lista*** activada), y luego hacer clic en la opción ***Seleccionar de la lista*** en la pestaña ***General*** y vincularla a un conjunto específico de credenciales de la lista.

Existen muchos casos de uso para esta función, pero una de las principales ventajas de la vinculación dinámica de credenciales es hacer que los usuarios utilicen el conjunto de credenciales adecuado para sus necesidades sin que se les muestre una lista para elegir.

**Véase también**

* [Devolutions Academy – Configure dynamic credential linking in Remote Desktop Manager](https://academy.devolutions.net/student/activity/3345713-configure-dynamic-credential-linking-in-remote-desktop-manager)


---

# 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/es/knowledge-base/knowledge-base-articles/dynamic-credential-linking.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.