> 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/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/manage-dashboards-and-reports/reports.md).

# Reports

The **Reports** page is your central hub for organizing and managing your reports. It is split into two tabs, allowing you to quickly browse your report history or configure report templates:

* **Generated Reports**: View a list of all completed reports and download them as needed. For reports with attachments, the **Name** field indicates the number of attached files.
* **Report Templates**: View all report templates you have access to, including system templates and custom templates created by you or shared with you.

From the **Reports** page, you can perform the following tasks on your report templates:

* **Create templates**: Create a new report template from scratch in the report builder.
* **Generate reports**: Run any report template to immediately generate and download a report.

{% hint style="info" %}
**Data scoping:** Reports pre-fetch data based on the scope of the user who last saved the template. Ensure the template creator has the appropriate data permissions to provide the intended results for the report recipients.
{% endhint %}

* **Edit templates**: Rename the template, update its description, adjust the layout, or modify widget data.
* **Duplicate**: Create a copy of an existing template to use as a starting point for a new version.
* **Import**: Import report configurations in JSON format.
* **Export**: Export the report template configuration as a JSON file.
* **Manage access**: Share custom templates with other users, groups, or API keys. Custom templates are **Restricted** by default but can be assigned the following visibility levels:
  * **Public**: Visible to all users with the appropriate role permissions to view reports.
  * **Restricted**: Visible only to the template owner and specific authorized users or groups.

Icons in the **Source** column can help you to identify the security access and status of your reports. For more information, see [Access and visibility for dashboards and reports](/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/access-and-visibility-for-dashboards-and-reports.md).


---

# 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/data-security-documentation/inventory-and-monitoring/dashboards-and-reports/manage-dashboards-and-reports/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.