> 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/reports/create-a-new-report.md).

# Create a new report

Create a new report template from scratch or by modifying an existing report template.

You can create a new report template from scratch or by modifying an existing report template. You can also schedule reports to run regularly.

1. Go to Reports → Reports Templates and select **+New Template**.
2. Enter a unique **Report Name** and an optional **Description** of the report.
3. Select the **Data Timeframe** for your report.

   You can choose **Last 24H** (day), **Last 7D** (week), **Last 1M** (month), or you can choose a custom timeframe.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>The custom timeframe is limited to one month.</p></div>
4. Choose the **Report Type**.

   Use an existing template or build the new report template from scratch.
5. Click **Next**.
6. Customize your report.

   Drag and drop widgets from the widgets library to the desired position in the report template.

   Click the options icon ![menu\_options\_button.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-331c8c3490835539d195f8e04f03b118319faf9c%2F14295c9ed3582f910adab35625272fabebd445feea2f94953c97bab3f3569464.png?alt=media) in the top right corner of a widget to customize the widget or remove the widget from the template.

   To get a feel for how the data will look, Cortex Xpanse provides mock data. To see how the report would look with real data in your environment, you can use the toggle above the report to use **Real Data**. Select **Preview A4** to view how the report is displayed in an A4 format.
7. Click **Next**.
8. If you are ready to run the report, select **Generate now**.
9. To run the report on a regular **Schedule**, you can specify the time and frequency that Cortex Xpanse will run the report.
10. (Optional) Enter an **Email Distribution** list or **Slack workspace** to send a PDF version of your report.

    Select **Add password used to access report sent by email and Slack** to set password encryption.

    <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Password encryption is only available in PDF format.</p></div>
11. (Optional) **Attach CSV** file of your XQL query widget to a report.

    From the drop-down menu, search and select one or more of your custom widgets to attach to the report. The XQL query widget is attached to the report as a CSV file along with the customized PDF. Depending on how you selected to send the report, the CSV file is attached as follows:

    * Email—Sent as separate attachments for each widget. The total size of the attachment in the email cannot exceed 20MB.
    * Slack—Sent within a ZIP file that includes the PDF file.
12. **Save Template**.
13. After your report generates, you can download it from the Report → **Reports** page.


---

# 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/reports/create-a-new-report.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.