> 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/onboard-and-configure/post-deployment-steps/dashboards-and-reports.md).

# Dashboards and reports

Create and manage Cortex Cloud dashboards and reports for security visibility and analysis.

Dashboards consist of visualized data powered by fully customizable widgets, which enable you to analyze data from inside or outside Cortex Cloud, in different formats such as graphs, pie charts, or text. Cortex Cloud displays the predefined dashboards when you log in. You can also create custom dashboards that are based on the predefined dashboards, or built to your specifications, and you can save any of your dashboards as reports.

From the **Dashboard & Reports** menu, you can view and manage your dashboards and reports from the dashboard and incidents table, and view alert exclusions.

* **Dashboard:** Provides dashboards that you can use to view high-level statistics about your agents and incidents.
* **Reports:** View all the reports that Cortex Cloud administrators have run.
* **Customize:** Create and manage a new dashboard and reports.
  * **Dashboards Manager:** Add new dashboards with customized widgets to surface the statistics that matter to you most.
  * **Reports Templates:** Build reports using pre-defined templates, or customize a report. Reports can be generated on-demand scheduled.
  * **Widget Library:** Search, view, edit, and create widgets based on predefined widgets and user-created custom widgets.


---

# 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/onboard-and-configure/post-deployment-steps/dashboards-and-reports.md?ask=<question>&goal=<user_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.
