> 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/server/da/web-interface/administration/modules/privileged-access/account-lifecycle-policies.md).

# Politikker for kontolevetid

Opret politikker for kontolevetid i Devolutions Server PAM for at konfigurere rotation af adgangskoder, heartbeat-planer og udbredelsesscripts for udbyderkonti.

Afsnittet ***Politikker for kontolevetid*** giver administratorer mulighed for at oprette og redigere særskilte politikker for kontolevetid, rotation af adgangskoder, heartbeat-plan og udbredelse. Politikkerne kan anvendes direkte på bestemte udbydere (under ***Administration*** – ***Privilegeret adgangsstyring (PAM)*** – ***Rediger*** – ***Politik for kontolevetid***) eller konfigureres, så de anvendes som standard på alle konti.

<table><thead><tr><th width="242">INDSTILLINGER</th><th>BESKRIVELSER</th></tr></thead><tbody><tr><td><strong>Navn</strong></td><td>Angiv et navn til politikken for kontolevetid.</td></tr><tr><td><strong>Angiv som standard</strong></td><td>Anvend politikken for kontolevetid på alle kontoudbydere som standard.</td></tr><tr><td><strong>Tilstand for adgangskodepolitik</strong></td><td>Aktivér/deaktiver adgangskodepolitikken.</td></tr><tr><td><strong>Adgangskodepolitik</strong></td><td>Vælg en adgangskodepolitik. Der skal tidligere være oprettet politikker under <em><strong>Administration</strong></em> – <em><strong>Adgangskodepolitik.</strong></em></td></tr><tr><td><strong>Handling ved indtjekning</strong></td><td>Definer en handling, der skal udføres, når en post tjekkes ind.</td></tr><tr><td><strong>Manuel rotation af adgangskode</strong></td><td>Aktivér/deaktiver manuel rotation af adgangskode. For at rotere en adgangskode manuelt gås der til den post, der skal roteres, der klikkes på <em><strong>Mere</strong></em> (knappen med lodret ellipse), og der vælges <em><strong>Nulstil adgangskode</strong></em>.</td></tr><tr><td><strong>Plan for rotation af adgangskode</strong></td><td>Angiv en plan for automatisk rotation af adgangskode.</td></tr><tr><td><strong>Heartbeat</strong></td><td>Aktivér/deaktiver heartbeat.</td></tr><tr><td><strong>Heartbeat-plan</strong></td><td>Angiv en plan for heartbeaten. Kræver <a href="/server/da/knowledge-base/knowledge-base-articles/scheduler-service-general-information.md">Planlægningstjeneste</a>.</td></tr><tr><td><strong>Udbredelse</strong></td><td>Vælg et udbredelsesscript, forudsat at der er oprettet et under <em><strong>Administration</strong></em> – <em><strong>Privilegeret adgangsstyring (PAM)</strong></em> – <em><strong>Udbredelse</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/server/da/web-interface/administration/modules/privileged-access/account-lifecycle-policies.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.