> 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/intermediate-concepts/reports.md). # Reports Devolutions Cloud reports provide audit views, scheduled exports, and password policy checks to help administrators monitor vault activity and compliance. Reports in Devolutions Cloud provide web based views and exports that help administrators audit activity, review logs, and manage deleted entries. Non administrative users have limited access, while administrators can run audits across vaults to support compliance and security reviews. The reporting service extends these capabilities with scheduled reports that run under an application identity and deliver outputs automatically by email or to external systems. Combined with password policies and privileged access reports, this enables continuous monitoring, for example listing weak passwords, expiring secrets, or PAM tasks that require attention. #### Related topics * [Reports](/cloud/web-interface/reports.md) * [Scheduled reports](/cloud/web-interface/reports/scheduled-reports.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/intermediate-concepts/reports.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.