> 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/concepts/basic-concepts/vaults.md). # Vaults Devolutions Cloud vaults partition entries into logical containers, such as shared or personal, with role-based permissions to securely share data. Vaults in Devolutions Cloud partition entries into logical containers so you can share the right data with the right users while keeping administration manageable. Each vault has its own content type, such as default, business, secrets, or credentials, which governs which entry types can be created there. Administrators configure vault-level permissions by assigning roles to users and user groups, and can create restricted access vaults for especially sensitive assets or choose a default vault for new users. A typical deployment combines shared team vaults for infrastructure or applications with a personal user vault for each user, giving them space for individual secrets while keeping organizational data clearly segmented. #### Related topics * [Create and manage vaults](/cloud/web-interface/administration/management/vaults/create-and-manage-vaults.md) * [Vault access in Devolutions Cloud](/cloud/web-interface/vault-access-in-devolutions-cloud.md) * [Vault privacy for administrators and users](https://docs.devolutions.net/resources/other-resources/vault-privacy-for-administrators-and-users) --- # 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/concepts/basic-concepts/vaults.md?ask=&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.