> 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/settings.md). # Settings Set default vault visibility, checkout policy, and account lifecycle policy values for Privileged Access Management in the Devolutions Server Settings section. The ***Setting*** section located in ***Administration*** – ***Privileged access management (PAM)*** allows administrators to determine the default checkout and account lifecycle policy settings.

DEFAULT VAULT VISIBILITY SETTINGS	DESCRIPTION
Default vault visibility	Determine whether users can see PAM vaults and request access by default, or if they need an invitation.

CHECKOUT POLICY SETTINGS	DESCRIPTIONS
Default checkout mode	Enable or disable checkouts by default.
Default approval mode	Define which requests require approval by default, if any.
Users can approve their own checkout requests	Choose whether users can approve their own requests, and under which condition.
Include admins as approver	Include all administrators in the list of approvers when checking out an entry.
Include PAM administrators when listing approvers	Include all PAM administrators in the list of approvers when checking out an entry.
Default reason mode	Choose under which conditions users need to give a reason for checking out an entry.
Default checkout time (minutes)	Set a default checkout time.
PAM default max checkout time (minutes)	Set a maximum checkout time. This is also the upper bound for the total duration of a checkout once extensions are applied.
Allow checkout extensions	Allow users to request additional time on an active checkout instead of checking in and submitting a new request. Disabled by default.
Require approval for extensions	Choose whether checkout extension requests must be approved, or are granted automatically.
Maximum extension duration (minutes)	Set the maximum additional time that can be granted for a single extension request.
Ticket number mode	Determine under which conditions the Ticket # field is required to be filled, if at all, when checking out an entry.
Terminate sessions on check in	Force session close on checkin.
Automatically check in PAM account when closing the entry	Force PAM account checkin when closing an entry it contains.

ACCOUNT LIFECYCLE POLICY SETTINGS	DESCRIPTIONS
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/settings.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.