> 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-cloud-posture-management/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/configure-the-issue-exception-approval-workflow.md).

# Configure the issue exception approval workflow

The following sections describe how to add or delete issue exception approvers and how to disable the issue exception approval workflow entirely, so that exception rules can be created without approvals.

## Add issue exception rule approvers

An exception rule approver must be added to the list of approvers in the system before an exception rule request can be sent to them. Exception approvers are not required to be Cortex XSIAM users. When you add a new approver to the list, that approver is sent an email notification indicating that they have been added to the approver list.

You can not be the approver of your own issue exception rule request.

{% hint style="warning" %}

### Prerequisite

You must have Exception Approver Admin permission to add or delete approvers.
{% endhint %}

1. Navigate to Settings>Configurations>Server Settings and scroll down to the Exception Management section.
2. Enter the approver’s name and email address, and then click Add New Approver.

The system will send the approver an email indicating that they have been added as an exception rule approver.

## Delete an issue exception rule approver

Consider the following restrictions when deleting issue exception rule approvers from the approver list:

* When the approval workflow is enabled, you cannot delete an approver if they are the only approver in the list. You must add a second approver before you can delete an approver.
* If an approver is linked to active or pending issue exception rules, you must disable those rules before you can delete the approver.

{% hint style="warning" %}

### Prerequisite

You must have Exception Approver Admin permission to add or delete approvers.
{% endhint %}

How to delete an issue exception rule approver

1. Navigate to **Settings** → **Configurations** → **Server Settings** and scroll to the **Exception Management** section.
2. Under **List of Approvers**, click the **X** next to the approvers name to delete them from the list.
3. **Save** the update.

## Disable the issue exception approval workflow

Disable the issue exception approval workflow to allow issue exceptions to be created without an approval.

{% hint style="warning" %}

### Prerequisite

You must have the Exception Approver Admin permission to disable or re-enable the issue exception approval workflow.
{% endhint %}

1. Navigate to **Settings** → **Configuration** → **General** → **Server Settings** and scroll to the **Exception Management** section.
2. Toggle Off **Approval Required**.

You can re-enable the issue exception approval workflow by toggling on Approval Required.


---

# 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-cloud-posture-management/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/configure-the-issue-exception-approval-workflow.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.