> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/dashboards-and-reports/monitor-dashboards-and-reports/overview-of-dashboards-and-reports.md). # Overview of dashboards and reports Learn the key concepts, interfaces, types, and widgets for dashboards and reports. Dashboards and reports help you monitor system activity and security operations across your environment. They summarize complex tenant activities into digestible graphical or tabular formats, allowing security analysts and administrators to effectively monitor cases, track data ingestion, and evaluate overall operational health. Dashboards provide an interactive interface for real-time monitoring, while reports deliver static snapshots optimized for historical tracking, auditing, and automated distribution. Access to both features is restricted by Role-Based Access Control (RBAC) and Scope-Based Access Control (SBAC) to maintain data security and tenant isolation. --- # 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/dashboards-and-reports/monitor-dashboards-and-reports/overview-of-dashboards-and-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.