> 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/threat-management-permissions/threat-intelligence-permissions.md).

# Threat Intelligence permissions

Configure permissions for Threat Intelligence.

Located under **Threat Management** → **Threat Intelligence**, these permissions govern how your organization interacts with indicators (IPs, URLs, Domains, Hashes) and intelligence feeds. It allows you to transform raw data from sources like Unit 42 or AlienVault into actionable security logic.

{% hint style="info" %}
This feature requires the Extended Threat Intelligence (XTI) security add-on.
{% endhint %}

For more information, see [Extended Threat Intelligence](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence.md).

| Component | Description                                                                                    |
| --------- | ---------------------------------------------------------------------------------------------- |
| None      | No access to the Threat Intel Library, Indicators and Threat Intel Dashboard.                  |
| View      | Users can search the Threat Intel Library and Indicators, and view the Threat Intel Dashboard. |
| View/Edit | Full control to manage indicators and indicator rules.                                         |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission      | Permission level | Reason                                                                                                                                    |
| --------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Cases & Issues  | View             | Strongly recommended. Indicator enrichment data appears in case artifacts, and editing indicators from case context requires case access. |
| Detection Rules | View/Edit        | Strongly Recommended. Enables creating indicator rules directly from indicators.                                                          |
| Query Center    | View/Edit        | Enables investigating indicators via XQL queries. Essential for validating indicator impact before creating rules or blocking.            |


---

# 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/threat-management-permissions/threat-intelligence-permissions.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.