> 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/folders.md). # Folders Devolutions Cloud folders organize vault entries into a hierarchy, such as Production or Staging, making credentials easier to find and manage securely. Folders in Devolutions Cloud organize entries within a vault so teams can mirror their infrastructure and quickly find the right secrets. Each folder appears in the Navigation pane tree of the selected vault and can contain entries or subfolders, for example grouping accounts by application, environment, or customer. When combined with shared vaults and roles, folders help limit who sees which entries while keeping a clear hierarchy across the web interface and companion tools like Remote Desktop Manager or the Devolutions Password Manager browser extension. For instance, you might maintain Production, Staging, and Development folders under a shared infrastructure vault, making it obvious where to store new credentials and where to search during incident response. #### Related topics * [Create entries manually](/cloud/web-interface/entries/create-entries-manually.md) * [Web interface](/cloud/web-interface.md) * [Create and manage vaults](/cloud/web-interface/administration/management/vaults/create-and-manage-vaults.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/cloud/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.