> 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/web-interface/administration/modules/privileged-access/account-lifecycle-policies.md). # Account lifecycle policies Create Account Lifecycle Policies in Devolutions Server PAM to configure password rotation, heartbeat schedules, and propagation scripts for provider accounts. The ***Account lifecycle policies*** section allows administrators to create and edit separate policies for account lifecycle, password rotations, heartbeat schedule, and propagation. These policies can be applied directly to specific providers (in ***Administration*** – ***Privileged access management (PAM)*** – ***Edit*** – ***Account lifecycle policy***), or configured to be applied by default to all accounts.

SETTINGS	DESCRIPTIONS
Name	Set a name for the account lifecycle policy.
Set as default	Apply the account lifecycle policy to every account provider by default.
Password policy mode	Enable/disable the password policy.
Password policy	Choose a password policy. Requires policies to have been created previously in Administration – Password policy.
Action on checkin	Define an action to be performed upon checking in an entry.
Manual password rotation	Enable/disable manual password rotation. To manually rotate a password, go to the entry to rotate, click More (vertical ellipsis button), and select Reset password.
Password rotation schedule	Set a schedule for automatic password rotation.
Heartbeat	Enable/disable heartbeat.
Heartbeat schedule	Set a schedule for the heartbeat. Requires the Scheduler service.
Propagation	Select a propagation script, provided one was created in Administration – Privileged access management (PAM) – Propagation.

--- # 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/web-interface/administration/modules/privileged-access/account-lifecycle-policies.md?ask=&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.