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

# Check-out approvals

Check-out approvals in Remote Desktop Manager restrict entry access to one user at a time and add optional approval workflows for accountability.

Check-out approvals help avoid user conflicts by limiting access to authorized users and, if configured, adding an approval workflow. While checked out, others cannot open it until it is checked back in, reducing errors and credential exposure.

For additional control, require approval to grant time-bound access to users who normally lack permission. Combine check-outs with role-based access control and detailed auditing to ensure accountability and traceability across your environment.

#### Related topics

* [Checkout system](/rdm/ribbon-menu-bar/edit/checkout-system.md)
* [Request temporary access to an entry in Remote Desktop Manager](/rdm/user-interface/content-area/temporary-access-in-remote-desktop-manager/request-temporary-access-to-an-entry-in-remote-desktop-manager.md)
* [Vault access in Remote Desktop Manager](/rdm/user-interface/content-area/vault-access-in-remote-desktop-manager.md)

#### See also

* [Easily Elevate Permissions with RDM's Temporary Access feature - RDM Pro Tip 020](https://youtu.be/En3pmonz1f8?si=7YbxYSgW5Y1PfZf6)
* [Devolutions Academy - Use the Checkout System in Remote Desktop Manager](https://academy.devolutions.net/student/page/3487229-use-the-checkout-system-in-remote-desktop-manager?curriculum_activity_id=5561271\&path_id=2628397\&sid=3b192113-2064-4d43-8ecd-5ea0c18168ee\&sid_i=0)


---

# 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/rdm/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.