> 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/administration/management/vaults.md).

# Vaults

Understand Devolutions Cloud vaults, including the shared default vault and the personal user vault, plus recommended entry limits.

***Vaults*** are containers for your entries, your credentials, sensitive information, sessions, and more.

You will start with two:

* One main ***default vault*** created for sharing entries to team members that you grant access to. You can add and share more vaults in ***Administration – Vaults***.
* One ***user vault***, which is user centric and is used to store information such as personal account credentials. The ***user vault*** prevents users from using a non-secure tool to manage their personal passwords at work. The ***user vault*** can be disabled in ***Administration – System Settings***.

{% hint style="success" %}
Loading vaults with a high number of entries (i.e., over 2000) can cause performance issues, and it is therefore recommended to organize entries across multiple vaults. There is no limit to the number of vaults that can be created.
{% endhint %}

#### See also

* [Devolutions Academy – Working with your vaults](https://academy.devolutions.net/student/page/2640024-working-with-your-vaults?curriculum_activity_id=4269754\&path_id=2543918\&sid=9a068cf7-780c-4a2b-8f00-61f18d3f7325\&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/cloud/web-interface/administration/management/vaults.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.