> 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/checkout-system.md).

# Checkout system

Lock entries during use with the Devolutions Server checkout system, preventing simultaneous edits and enabling force check-in and multiple checkouts.

The ***Checkout system*** locks an entry while it is being used or modified, preventing multiple users from using or editing it at the same time.

It can be enabled for ***General***, ***Session***, ***Information***, and ***Credential*** entries.

### Check out an entry <a href="#check-out-an-entry" id="check-out-an-entry"></a>

1. In the ***Navigation pane***, select an entry.
2. Click ***Check Out***.
3. Enter a ***Comment*** explaining why you are checking out the entry.
4. Optional: enable ***Automatic check in after*** and set a duration in minutes.
5. Click ***OK***.

An information banner appears at the top of the entry, and an icon displays in the ***Navigation pane*** to indicate that the entry is checked out. If the entry has a linked credential or a linked one-time password (OTP) entry, checking out the entry also checks those out, under the same prompt (a note indicates how many additional entries will be checked out).

Copying information that is already visible without a checkout, such as the username or domain, does not require checking out the entry. Copying or revealing the password (or a linked OTP) still requires it.

### Check in an entry <a href="#check-in-an-entry" id="check-in-an-entry"></a>

1. In the ***Navigation pane***, select the checked-out entry.
2. Click ***Check in***.

By default, ***Check in*** only checks in the current user's own checkout. If the entry has no checkout from the current user but is checked out by others, and the current user has the ***Check in (force)*** permission, the button becomes ***Force Check-in*** instead. If several users have checked out the entry, a ***Select checkouts to check in*** window lets you choose which checkouts to release.

### Check out or check in a folder <a href="#check-out-or-check-in-a-folder" id="check-out-or-check-in-a-folder"></a>

Checking out or checking in a folder, or an entry with sub-entries, opens a window listing the entries it contains as a checklist. Use:

* ***Checkout folder only*** / ***Check in folder only*** to act on the folder (or parent entry) alone.
* ***Checkout contents of folder only*** / ***Check in contents of folder only*** to act on its contents without the folder (or parent entry) itself.
* The checklist itself, to check out or check in a custom selection.

An entry with sub-entries is handled the same way, with the parent entry treated as the folder.

### Check out or check in multiple entries <a href="#check-out-or-check-in-multiple-entries" id="check-out-or-check-in-multiple-entries"></a>

Selecting multiple entries and choosing ***Check out*** or ***Check in*** from the context menu applies a single comment and duration to the whole selection. Once the operation completes:

* If every entry succeeds, a notification reports how many entries were checked out or checked in.
* If every entry fails, a notification explains why.
* If some entries fail while others succeed, a window lists the failed entries and the reason for each.

{% hint style="info" %}
Forcing the check-in of a multi-selection or a folder's contents checks in every checkout on every selected entry, including checkouts held by other users, after a warning.
{% endhint %}

### Simultaneous checkouts <a href="#simultaneous-checkouts" id="simultaneous-checkouts"></a>

The ***Multiple checkouts*** setting allows multiple users to check out and edit the same entries simultaneously. It is only configurable at the vault level: go into the properties of the vault's root folder and navigate to ***Security settings – Multiple checkouts***. All entries and folders in the vault follow this setting.

| OPTION       | DESCRIPTION                                                                              |
| ------------ | ---------------------------------------------------------------------------------------- |
| **Default**  | Behaves as **Off**.                                                                      |
| **Off**      | Disables ***Multiple checkouts***.                                                       |
| **Infinite** | Allows users to check out the same entry simultaneously without restriction.             |
| **Custom**   | Lets you define the maximum number of users who can check out an entry at the same time. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/server/web-interface/checkout-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.