> 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/pam/concepts/check-out-and-check-in.md).

# Check-out and check-in

Check-out and check-in in Devolutions PAM reserve privileged accounts for exclusive use and rotate passwords automatically after each session.

**Check-out** and **check-in** are processes used to secure and manage [privileged accounts](/pam/concepts/privileged-account.md). **Check-out** refers to reserving a privileged account for exclusive use, effectively locking it from access by others. When enabled, MFA can also be required at the moment of check-out, prompting users to verify their identity with a second factor before a privileged session is launched.

**Check-in** releases this lock, typically followed by a [password rotation](/pam/concepts/password-rotation.md) to ensure account security. This mechanism ensures that credentials are not reused without oversight.

Check-in can occur manually, automatically at the end of the check-out period, or when a session is closed in Remote Desktop Manager, depending on user configuration. This provides flexibility while helping to enforce secure practices. With [just-in-time (JIT) access](/pam/concepts/just-in-time-elevation.md), group or role memberships of privileged accounts are temporarily modified upon check-out and restored on check-in, limiting access to only what is needed during the session.

This functionality supports secure, time-bound access to sensitive resources, helping organizations control and monitor privileged usage, especially when combined with logging and session auditing features in Devolutions APM and Devolutions Server.

#### Aliases

* Account retrieval (CyberArk)
* Privileged account reservation

#### Related topics <a href="#related-topics" id="related-topics"></a>

* [Approve access to a privileged account in Devolutions Cloud](/pam/pam-with-devolutions-cloud/privileged-accounts/approve-access-to-a-privileged-account.md)
* [Request access to a privileged account in Devolutions Cloud](/pam/pam-with-devolutions-cloud/privileged-accounts/request-access-to-a-privileged-account.md)
* [Check-out requests report in Devolutions Cloud](/pam/pam-with-devolutions-cloud/privileged-access-reports/check-out-requests.md)

#### See also <a href="#see-also" id="see-also"></a>

* [Privileged accounts (Devolutions Server)](/pam/pam-with-devolutions-server/privileged-accounts.md)
* [Privileged accounts (Devolutions Cloud)](/pam/pam-with-devolutions-cloud/privileged-accounts.md)
* [Spotlight on automatic privileged account check-in](https://blog.devolutions.net/2024/11/inside-20243-automatic-privileged-account-check-in/)
* [Glossary of Common Privileged Access Management (PAM) Terms](https://blog.devolutions.net/2021/01/glossary-of-common-privileged-access-management-pam-terms/)
* [Need Cybersecurity Insurance? Then You Probably Need PAM, Too](https://blog.devolutions.net/2023/10/need-cybersecurity-insurance-then-you-probably-need-pam-too/)


---

# 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/pam/concepts/check-out-and-check-in.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.