> 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-xpanse/dashboards-and-reports/dashboards/manage-dashboards.md).

# Manage dashboards

From Dashboards Manager, you can delete, edit, disable, and perform additional management actions on your dashboards.

From the **Dashboards Manager**, you can delete, edit, duplicate, disable, and perform additional management actions on your dashboards.

1. Navigate to **Dashboards** → **Dashboards Manager** to view all custom and predefined dashboards.
2. Right-click a dashboard, and select from the following actions:
   * **Delete** - Permanently delete a dashboard.
   * **Edit** - Edit an existing dashboard. You cannot edit the default dashboards provided by Palo Alto Networks, but you can save them as new dashboards.
   * **Save as new** - Duplicate an existing dashboard, and save it with a new name.
   * **Disable** - Temporarily disable a dashboard. If the dashboard is public, this dashboard is also removed for all users.
   * **Set as default** - Make the dashboard the default dashboard that displays when you (and other users, if the dashboard is public) log in to Cortex Xpanse .
   * **Save as report template** - Save the dashboard as a report template.


---

# 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-xpanse/dashboards-and-reports/dashboards/manage-dashboards.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.