> 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-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-customization.md).

# Threat Intel Reports Customization

Set up and customize threat intelligence report types in Cortex XSOAR 6.15.

When creating a threat intel report, you can use one of the out-of-the-box report types, customize an out-of-the-box report type, or create your own report type.

Each report type has an associated layout, containing relevant fields.

Before you begin setting up and customizing threat intel reports, consider the following elements involved in creating report types:

| Element                                                                                                                                                                 | Description                                                                                                                                                    |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Types](/cortex-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-customization/configure-threat-intel-report-types.md)     | Determine which report types your organization needs. Each type has an associated layout. You choose a type when you create a report.                          |
| [Fields](/cortex-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-customization/configure-threat-intel-report-fields.md)   | Use as placeholders to manually populate a report with relevant data after a report is created. Fields are included with, and can be added to, report layouts. |
| [Layouts](/cortex-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-customization/configure-threat-intel-report-layouts.md) | Customize your layouts for each report type to make sure the most relevant information is shown for each type.                                                 |

{% hint style="info" %}
By default, when editing the following inline values in a threat intel report, the changes are not saved until you confirm your changes (clicking the checkmark icon in the value field).

These icons are designed to let you have an additional level of security before you make changes to the fields in threat intel reports, incidents, and indicators.

To change the default behavior, set the **`inline.edit.on.blur`** server configuration to **`true`**, which enables you to make changes to inline fields without clicking the checkmark. The changes are automatically saved when clicking anywhere on the page or when navigating to another page. For text values, you can also click anywhere in the value field to edit.
{% endhint %}


---

# 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-xsoar-6-threat-intel-management-guides/6.15/reports/threat-intel-reports/threat-intel-reports-customization.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.