> 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-agentix/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/dashboard-reference/command-center-reference.md).

# Command Center reference

Reference Command Center dashboards for security operations in Cortex AgentiX.

The platform provides a collection of pre-configured Command Centers designed to give you comprehensive visibility across your enterprise's security architecture.

{% hint style="info" %}

### Note

Access to these dashboards requires RBAC permissions under **Dashboards & Reports**. The **Dashboards** component must be **Enabled** in your role and requires **View** permissions for **Command Center Dashboards**. If certain options are unavailable, contact your administrator.
{% endhint %}

| Command Center                         | Operational Description                                                                                                                                          |
| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cortex Agentic Assistant Dashboard** | Maximize AI automation. Monitor how AI agents power your SOC, identify your most active security use cases, and find new opportunities to automate manual tasks. |
| **Cortex Cloud Command Center**        | Monitor cloud status. Functions as a live, single-pane-of-glass workspace showing the overall health and security status of multi-cloud infrastructures.         |


---

# 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-agentix/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/dashboard-reference/command-center-reference.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.