> 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-xsoar-8-on-prem/8.13/configure-cortex-xsoar/dashboards-and-reports/dashboards.md). # Dashboards Create and manage dashboards in Cortex XSOAR 8.13 On-prem. Dashboards offer graphical overviews of your tenant's activities, enabling you to effectively monitor incidents and overall activity in your environment. Each dashboard comprises widgets that summarize information about your endpoint in graphical or tabular format. #### Default dashboards Cortex XSOAR provides several out-of-the-box dashboards, including the following: {% hint style="info" %} ### Note If you install a content pack which contain dashboards, these can be added from the **More Dashboards** dropdown. To change the order of the dashboards, hover over the six block icon next to a dashboard name. When the cursor turns into a hand, drag and drop the dashboard into the required location. {% endhint %} | Dashboard | Description | | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | My Dashboard | A personalized dashboard showing your incidents, tasks, etc. | | My Threat Landscape | Information about malicious/suspicious indicators in incidents, top 10 indicators in related incidents, Unit 42 feed (if enabled). | | SLA | Information about your Service Level Agreements. | | Troubleshooting Playbooks | Information about playbook run and execution errors. | | Incidents | Information about incidents, such as severity type, active incidents, unassigned incidents, etc. | | API Execution Metrics | Information about API calls. You can use the **API Execution Metrics for Enrichment Command** widget for troubleshooting and to make decisions about indicator enrichment. | | Cost Optimization Playbooks | Information about playbooks including task executions, average runtime, etc. | | Troubleshooting Instances | Information about integration instance errors. | | Threat Intelligence Feeds | Information about TIM feeds that are being ingested into Cortex XSOAR. | | Cost Optimization Instances | Information about commands that have been executed in Cortex XSOAR. | | MITRE ATT\&CK |

Information about MITRE ATT\&CK techniques. Part of the MITRE ATT\&CK content pack.

Note

You can add this to your displayed dashboards when clicking More dashboards.

| | Threat Intel Management |

Information about active indicators by reputation, type, expired indicators, etc.

Note

You can add this to your displayed dashboards when clicking More dashboards.

| | VirusTotal API Execution Metrics |

Information about VirusTotal API commands. Part of the VirusTotal content pack.

Note

You can add this to your displayed dashboards when clicking More dashboards.

| --- # 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-xsoar-8-on-prem/8.13/configure-cortex-xsoar/dashboards-and-reports/dashboards.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.