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

# Dynamisk sammenkædning af legitimationsoplysninger

Brug dynamisk tilknytning af legitimationsoplysninger i Remote Desktop Manager til at knytte en sessionspost til ét bestemt sæt legitimationsoplysninger fra en liste, der vises.

Dynamisk tilknytning af legitimationsoplysninger i Remote Desktop Manager er det at knytte en sessionspost til en legitimationspost, der normalt viser en liste for brugeren (f.eks. ***Adgangskodeliste*** eller ***LastPass*** med indstillingen ***Spørg altid med liste*** aktiveret), og derefter klikke på indstillingen ***Vælg fra liste*** på fanen ***Generelt*** og knytte til et bestemt sæt legitimationsoplysninger fra listen.

Der er mange brugsscenarier for denne funktion, men en af de vigtigste fordele ved dynamisk tilknytning af legitimationsoplysninger er, at brugerne bruger det rigtige sæt legitimationsoplysninger til deres behov uden at få vist en liste, de skal vælge fra.

**Se også**

* [Devolutions Academy – Konfigurer dynamisk tilknytning af legitimationsoplysninger i 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/da/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.