> 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/concepts/basic-concepts/folders.md). # Folders Folders in Devolutions Server organize vault entries by environment, business unit, or customer, forming a boundary for delegating permissions. Folders organize entries inside a vault in Devolutions Server and provide a natural boundary for delegating permissions and temporary access. They let you mirror your organizational structure, for example by environment, business unit, or customer, while keeping navigation simple for end users. Security is typically applied at the folder level, with user group based security inheriting rights to child folders and entries but allowing overrides where needed. A common pattern is a top level folder per customer, subfolders for infrastructure and passwords, and a restricted subfolder for privileged accounts. #### Related topics * [Entries](/server/web-interface/vaults/entries.md) * [User groups based security](/server/web-interface/user-group-based-security.md) --- # 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/concepts/basic-concepts/folders.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.