> 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/cloud/web-interface/entries/checkout-system.md).

# Checkout system

Use the Devolutions Cloud checkout system to lock entries during use, prevent editing conflicts, and configure multiple checkout settings.

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

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

#### Check out an entry

1. Select an entry.
2. Click ***Check out***.
3. ***Comment*** why you are checking out the entry.
4. Optional: enable ***Automatic check in after*** a number of minutes.
5. Click ***OK***.

An information banner at the top of the entry and an icon in the ***navigation pane*** will appear to warn the users that this 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

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 other users, and the current user has the ***Force checkin*** permission, checking in instead force checks in **every** checkout currently held on that entry at once, after a confirmation showing how many users currently hold it.

#### Check out or check in a folder

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*** (or ***Checkout parent only*** for sub-entries) to act on the folder or parent entry alone.
* ***Checkout contents of folder only*** (or ***Checkout contents of parent 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.

#### Check out or check in multiple entries

Selecting multiple entries and choosing ***Check out*** or ***Check in*** 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 ***Checkout result*** window lists the failed entries and the reason for each.

## 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 object 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/cloud/web-interface/entries/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.