> 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/entry-settings/sticky-password.md).

# Sticky Password

Konfigurer legitimationsposten Sticky Password i Remote Desktop Manager, herunder kontoens e-mail, hovedadgangskode og de gemte legitimationsoplysninger, der skal bruges.

Denne artikel beskriver de mange indstillinger og valgmuligheder, der er tilgængelige for legitimationsposter ***Sticky Password*** i Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>INDSTILLINGER</strong></td><td><strong>BESKRIVELSE</strong></td></tr><tr><td><strong>Navn</strong></td><td>Navnet på posten.</td></tr><tr><td><strong>Mappe</strong></td><td>Den mappe, hvor posten findes. Klik på knappen Gennemse for at vælge en mappe, eller klik på knappen Tilføj (<em><strong>+</strong></em>) for at oprette en ny.</td></tr></tbody></table>

### Generelt

<table><thead><tr><th width="220">INDSTILLINGER</th><th>BESKRIVELSE</th></tr></thead><tbody><tr><td><strong>Mail</strong></td><td>Angiv e-mailadressen for Sticky Password-kontoen. Dette felt er obligatorisk.</td></tr><tr><td><strong>Hovedadgangskode</strong></td><td>Angiv hovedadgangskoden for Sticky Password-kontoen. Dette felt er obligatorisk, medmindre <em><strong>Spørg altid om adgangskode</strong></em> er markeret. Det er utilgængeligt, når <em><strong>Spørg altid om adgangskode</strong></em> er markeret, eller når systemindstillingen <em><strong>Deaktiver lagring af adgangskode i bokse</strong></em> er aktiveret.</td></tr><tr><td><strong>Spørg altid om adgangskode</strong></td><td>Når denne indstilling er markeret, gemmes hovedadgangskoden ikke i posten. De bliver bedt om at angive den, hver gang der er brug for den.</td></tr><tr><td><strong>Legitimationsoplysninger</strong></td><td>Vælg de legitimationsoplysninger, der er gemt i Sticky Password. Klik på knappen Gennemse for at vælge på listen. Når <em><strong>Spørg altid om adgangskode</strong></em> er markeret, bliver De bedt om hovedadgangskoden, før listen åbnes. Et valg er obligatorisk, medmindre <em><strong>Spørg altid med liste</strong></em> er markeret. Dette felt er utilgængeligt, når <em><strong>Spørg altid med liste</strong></em> er markeret.</td></tr><tr><td><strong>Spørg altid med liste</strong></td><td>Når denne indstilling er markeret, får De vist en liste over de legitimationsoplysninger, der er gemt i Sticky Password, hver gang De bruger posten, i stedet for de legitimationsoplysninger, der er valgt i feltet <em><strong>Legitimationsoplysninger</strong></em>.</td></tr></tbody></table>


---

# 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/entry-settings/sticky-password.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.