> 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/administration/user-and-security-management/vaults/general.md). # General Configure general vault settings in Devolutions Server, including name, description, visibility, security level, and vault content type restrictions. ### Edit vault settings
OPTIONDESCRIPTION
NameVault's name.
DescriptionVault's description.
Sort priorityThe sort priority changes the vault order in the navigation pane to the left of the Web interface. 0 is the default, higher values place the vault nearer the top of the list.
VisibilityChoose whether to allow the vault to be visible by invitation only, or to allow access requests.
Security level
  • Standard security level: The offline mode can be enabled.
  • High security level: The offline mode is disabled for this vault. Credentials are fetched from the server exclusively at use time.
Vault content typeChoose a vault content type (everything, secrets, credentials, or business information). Vault content types limit the entry types that can be created in this specific vault.
--- # 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/server/web-interface/administration/user-and-security-management/vaults/general.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.