> 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-xsiam/reference-and-developer-docs/role-based-access-control/exceptions-configuration-permissions/exception-management-admin-permissions.md).

# Exception Management Admin permissions

Configure Exception Management Admin permissions in Cortex XSIAM.

Exception Management Admin controls access to the **Exception Rules** tab on the **Issue Exclusions & Exceptions** page. Exception rules differ from exclusion rules in that they define conditions under which issues are flagged as exceptions that may require approval before being acted upon, rather than being silently suppressed.

####  Navigate to the **Issue Exception & Exclusion** page

{% hint style="info" %}
**Prerequisite:** Requires **Issue Exclusions** permission (at least View) to access the page. Without Issue Exclusions, the entire page is hidden.
{% endhint %}

The navigation path depends on your RBAC permissions and tenant configuration. Take one of the following paths:

* **Settings** →  **Issue Exception & Exclusion**
* **Settings** → **Exception Management** → **Issue Exception & Exclusion**
* **Settings** → **Exception Configurations**

On this page you can see the following tabs:

* **Exclusion Rules:** Defines conditions (based on issue attributes, such as severity, source, category, etc.) that automatically suppress the creation or surfacing of matching issues. This is the primary mechanism for tuning out false positives and reducing issue noise.
* **Exception Rules:** Defines conditions under which issues are flagged as exceptions that may require approval before being acted upon, rather than being silently suppressed.

### Exception Management Admin permission levels

<table><thead><tr><th width="101">Permission</th><th>Description</th><th>Roles Example</th></tr></thead><tbody><tr><td>None</td><td><p></p><ul><li>No access to the <strong>Exception Rules</strong> tab on the <strong>Issue Exception &#x26; Exclusion</strong> page.</li><li>No access to issue exception actions anywhere in Cortex XSIAM.</li></ul></td><td>SOC Tier-1 Analyst: Should escalate false positives rather than create an exception.</td></tr><tr><td>View</td><td><p></p><ul><li>Read-only access to the <strong>Exception Rules</strong> tab on the <strong>Issue Exception &#x26; Exclusion</strong> page. </li><li>Users can browse the <strong>Exception Rules</strong> tab, view rule details (name, description, indicator conditions, BIOC indicator definitions, and filter/search the exception rules grid. </li><li>No access to create or disable exception rules.</li></ul></td><td>SOC Tier-2 Analyst and Threat Hunter: Should reference existing exceptions during investigations or understand filtered activity.</td></tr><tr><td>View/Edit</td><td><p></p><ul><li>Read and write access to the <strong>Exception Rules</strong> tab on the <strong>Issue Exception &#x26; Exclusion</strong> page. </li><li>Users can create, edit, delete, enable, import, and duplicate exception rules </li><li>Users can create issue exceptions via the <strong>Issues</strong> and <strong>Cases</strong> pages.</li></ul></td><td><ul><li>SOC Tier-3 Analyst: Create exception rules for validated false positives.</li><li>Security Engineer: Manage exception rules as part of tuning.</li></ul></td></tr></tbody></table>

#### **Required and recommended permissions**

Consider adding the following permissions:

<table><thead><tr><th width="152">Permission</th><th width="143.9998779296875">Permission Level</th><th>Reason</th></tr></thead><tbody><tr><td>Cases &#x26; Issues</td><td>View</td><td>Exception rules are based on issue attributes. Without alert visibility, users cannot understand the context of what is being excepted. Required.</td></tr><tr><td>Issue Exclusions</td><td>View or View/Edit</td><td><ul><li><strong>View:</strong> <strong>Issue Exclusions</strong> is a prerequisite. It controls access to the <strong>Issue Exclusions and Exceptions</strong> page. Without it, the page is hidden, and the <strong>Exception Rules</strong> tab cannot be reached. Required.</li><li><strong>View/Edit:</strong> Users who manage exception rules typically also need to manage exclusion rules. Having both at View/Edit provides a complete exception management workflow.</li></ul></td></tr></tbody></table>


---

# 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-xsiam/reference-and-developer-docs/role-based-access-control/exceptions-configuration-permissions/exception-management-admin-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.