> 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/create-an-incident-summary-report.md).

# Create an Incident Summary Report

Create incident summary reports in Cortex XSOAR 6.12.

You can create and customize reports in PDF, CSV and Word formats based on the tabs in the **Incident** page. This enables you to capture investigation-specific data and share it with team members. You can customize how the information is displayed for existing incidents by modifying the sections and fields for each view. You can add a [new tab](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-customization.md) to an **Incident** page with the information configured specifically for creating reports.

You can save the reports as templates. Templates cannot be edited after they are created.

A list of the incident Summary Report templates appears in the **Reports** page under **Incident Reports**.

From the legacy Summary page, you can select and customize sections to export as a report. See [Select and Customize Sections to Export to a Summary Report](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/select-and-customize-sections-to-export-to-a-summary-report.md) for details.

1. Go to the **Incidents** page and select the incident for which you want to create a report.
2. Select the tab that has the information you want to appear in a report and click Actions → **Report**.
3. To build a new report, from the **Build Report** tab, select the following:
   * **Format**
   * **Orientation**

     It is recommend to use the landscape orientation to ensure that all information displays in the report.
   * **Paper Size**

     If you want to use the setting as a template, click the **Save report as template** check box.
4. To use an existing template, from the **Select a Template** tab, select the template.
5. To generate the report, click **Generate report** or use the following in a Playbook or as a CLI command:

   **`!GenerateSummaryReports name="`*****`<template name>`*****`" type="`*****`<report type>`*****`" ids="`*****`<Incident ID>`*****`"`**


---

# 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/create-an-incident-summary-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.