> 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-xdr-5.x/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/manage-dashboards-and-reports/import-and-export-dashboards-and-report-templates.md).

# Import and export dashboards and report templates

Import and export dashboards and report templates.

Administrators can export and import dashboards and report templates as JSON files. This allows you to quickly share configurations, back up content, or migrate settings between different environments. The system supports both single and bulk operations.

To perform these actions, navigate to the **Dashboard Manager** for dashboards, or the **Reports** page for report templates.

{% hint style="warning" %}
**Risk of data loss:** Importing a dashboard or report might overwrite the current version. To prevent accidental data loss, review your existing dashboards and report templates before proceeding with an import.
{% endhint %}

### Exporting dashboards & report templates

Before exporting, review the following requirements and system behaviors:

* **Infrastructure restrictions:** You cannot export dashboards built on custom infrastructure.
* **Access requirements:** To export a **Restricted** dashboard or report, you must have at least **Viewer** permissions.
* **Ownership & permissions stripping:** The exported JSON file contains only the configuration of the dashboard or template. It does not include the original access list or ownership data.

### Importing dashboards & report templates

When you import a JSON configuration, the system applies the following default rules:

* **Ownership:** You are automatically designated as the **Owner** of the imported dashboard or template.
* **Visibility:** Access is automatically set to **Restricted**. You must manually adjust the visibility settings if you want to share it. For more information, see [Visibility settings](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/access-and-visibility-for-dashboards-and-reports/visibility-settings.md).

### Troubleshooting "No Data" messages (XQL & Datasets)

Because dashboards rely on XQL (Cortex Query Language) to fetch data, imported widgets may display a **No Data** message if they reference datasets or log sources that do not exist in your environment.

**How to fix it:**

1. Edit the affected dashboard.
2. Locate the broken widgets and edit the XQL query.
3. Update the query syntax to match the exact dataset or log source names used in your current instance.


---

# 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-xdr-5.x/detect-investigate-and-respond-to-threats/monitor-dashboards-and-reports/manage-dashboards-and-reports/import-and-export-dashboards-and-report-templates.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.