> 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-8-on-prem/8.12/configure-cortex-xsoar/dashboards-and-reports/widgets/widget-customization.md).

# Widget customization

Cortex XSOAR provides out-of-the-box system widgets, such as **Late Incidents** and **Saved by Dbot (ROI Widget)**. You can edit these widgets when creating or editing a dashboard or report.

{% hint style="info" %}

### Note

Some content packs include a widget that tracks API rate limit errors. You can use this information for troubleshooting and to make decisions about indicator enrichment. From the Widgets Library, click **+** and choose **SOAR Metrics** from the dropdown. From the **Operations** tab, in the **Sum** field, select **Total API Calls**. In the **Group by** dropdown, select **API Response Type**. Note that this widget only displays data if there is an installed content pack that supports API rate limit information.
{% endhint %}

You can create custom widgets as follows and then add them to a dashboard or report as required.

| Widget customization method | Description                                                                                                                                                                                                                                                 |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Widgets Library             | <p>Create a widget using the widget builder in the <strong>Widgets Library</strong> which is available for all users.</p><p>For more information, see <a href="/pages/SOI77RWV4JrgrSEXN3Wb">Create a widget using the widget builder</a>.</p>               |
| From an incident            | <p>Create the widget from the <strong>Incidents</strong> page and then add it to a dashboard or a report.</p><p>For more information, see <a href="/pages/qyC2bXbaMW5TRDN9gA3m">Create a widget from an incident</a>.</p>                                   |
| From an indicator           | <p>Create the widget from the <strong>Threat Intel</strong> (<strong>Indicators</strong>) page and then add it to a dashboard or a report.</p><p>For more information, see <a href="/pages/Gu2rLkxlqNeyvfCEcBjJ">Create a widget from an indicator</a>.</p> |
| In the War Room             | <p>In the War Room, view an incident in widget format, for example, as severity in a bar chart.</p><p>For more information, see <a href="/pages/rD35LNxlDP4wHvGQxBvN">Add a widget in the War Room</a>.</p>                                                 |

{% hint style="info" %}

### Tip

We recommend the following to optimize performance.

* Keep widgets simple (no scripts)
* Set refresh times to greater than one minute
* Limit the number of widgets on a dashboard
  {% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/dashboards-and-reports/widgets/widget-customization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
