> 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/concepts/advanced-concepts/check-out-approvals.md).

# Check-out approvals

Check-out approvals in Devolutions Server require designated approvers to authorize privileged account requests in Devolutions PAM before checkout.

Check-out approvals in Devolutions Server with Devolutions PAM add an extra authorization step before a privileged account can be used. When a user requests to check out a PAM credential, the request is routed to designated approvers, who can approve or deny it with a reason and time limit, and every decision is fully logged.

Teams typically use check-out approvals for high-risk accounts such as domain admins, where a ticket number and manager approval are required before Remote Desktop Manager or Devolutions Gateway will open the session, helping align privileged access with internal controls.

#### Related topics

* [Check-out approvals](https://docs.devolutions.net/pam/concepts/check-out-approvals)
* [Checkout process](https://docs.devolutions.net/pam/pam-with-devolutions-server/checkout-process)
* [Temporary access in Devolutions Server](https://docs.devolutions.net/server/web-interface/temporary-access-in-devolutions-server.md)


---

# 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/concepts/advanced-concepts/check-out-approvals.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.
