> 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/search.md). # Search Devolutions Cloud search lets users quickly locate entries across all vaults from one view, while still respecting existing vault and role permissions. The Search section in Devolutions Cloud lets users quickly find entries across all vaults instead of browsing each folder manually. From the Search view, you can filter by entry name, jump back to recently viewed items, and open entries directly for launch or editing. Results always respect the underlying vault and role permissions, so users only see entries they are allowed to access, whether they are working in the web interface or using Remote Desktop Manager or Devolutions Password Manager. During incident response, for example, an operator can search for a host name or account alias and immediately navigate to the corresponding sessions, credentials, and documentation without needing to know which vault holds them. #### Related topics * [Search](/cloud/web-interface/search.md) * [Web interface](/cloud/web-interface.md) #### See also * [Devolutions Password Manager browser extension with Devolutions Cloud](https://docs.devolutions.net/password-manager/browser-extension/devolutions-password-manager-browser-extension-with-devolutions-cloud) --- # 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/search.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.