> 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/checkout-policies.md). # Checkout policies Define Checkout Policies for Privileged Access Management in Devolutions Server, controlling approval rules, checkout duration, MFA, and ticket enforcement. The ***Checkout policy*** section allows administrators to create and edit separate policies for Privileged Access Management (PAM) checkout. Checkout policies can then be applied to specific entries and folders (right-click, then ***Properties*** – ***Privileged access management (PAM)*** – ***Checkout policies***), or configured to be applied by default to everything. | SETTINGS | DESCRIPTIONS | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Set a name for the checkout policy. | | **Set as default** | Apply the checkout policy to every PAM entry/folder by default. | | **Checkout mode** | Enable or disable checkouts altogether. | | **Approval mode** | Define which requests require approval, 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. | | **Reason mode** | Choose under which conditions users need to give a reason for checking out an entry. | | **Checkout time (minutes)** | Set a default checkout time. | | **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. | | **MFA on checkout** | Require multifactor authentication when checking out an entry. Options are: ***Default***, ***None***, ***Mandatory***, or ***Mandatory on JIT elevation only***. The currently supported multifactor authenticators are Authenticator (TOTP), Email, and SMS. Multifactor authenticators must be [configured](/server/web-interface/administration/configuration/server-settings/security/multifactor.md) in ***Administration – Server settings – Multi-factor***. | | **Terminate sessions on check in** | Force session close on checkin. | --- # 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/checkout-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.