> 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/threat-management-permissions/detection-rules-permissions.md).

# Detection Rules permissions

Configure Cortex AgentiX permissions for viewing and managing correlation and indicator detection rules.

You can limit permissions for Detection rules (**Threat Management** → **Detection Rules**), which include the following:

* Correlations: Correlation rules that combine multiple events or conditions to detect complex attack patterns spanning multiple data sources or time periods.
* Indicator rules: Rules that automatically create IOC detection or prevention rules based on threat intelligence indicators matching specific criteria.

{% hint style="warning" %}

### Caution

Users must have View/Edit access to the Query Center to create or edit Correlation rules.
{% endhint %}

| Component | Description                                                                                | Roles Example                                                                                                                                                                                                                                                                                                                                                             |
| --------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None      | No access to Detection Rules.                                                              |                                                                                                                                                                                                                                                                                                                                                                           |
| View      | Read-only access to the Correlations page.                                                 | SOC Tier-1 analysts: Understand what rules are triggering issues.                                                                                                                                                                                                                                                                                                         |
| View/Edit | Full access to Detection rules, including creating, editing, deleting, and enabling rules. | <ul><li>SOC Tier 2 and 3 Analysts: Investigate cases and may need to create or modify detection rules based on findings.</li><li>Threat Hunter: Proactive threat detection specialists who search for hidden threats and create detection rules based on hunting findings.</li><li>Security Engineer: Full access to build and optimize detection capabilities.</li></ul> |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission     | Permission Level | Reason                                                                                                                                                                                                                                       |
| -------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Query Center   | View/Edit        | Required to edit Correlation Rules.                                                                                                                                                                                                          |
| Cases & Issues | View             | Strongly recommended. Detection rules generate issues that appear in Cases & Issues. Without case access, analysts cannot see the issues triggered by the rules they are viewing, losing critical context for rule effectiveness assessment. |


---

# 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-agentix/configure-cortex-agentix/users-and-roles-management/roles-management/role-permissions-by-component/threat-management-permissions/detection-rules-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.