> 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/exceptions-configuration-permissions/exception-approver-admin-permissions.md).
# Exception Approver Admin permissions
Configure Exception Approver Admin permissions in Cortex AgentiX.
Controls access to the **Exception Management** section on the **Server Settings** page, located at **Settings** → **Configurations** → **General** → **Server Settings**.
This permission governs who can configure the exception approval workflow, specifically, whether exceptions require approval, and managing the list of designated approvers.
{% hint style="warning" %}
### Caution
Users also need **General Configuration** View permission to view or View/Edit **Exception Management** in **Server Settings**.
{% endhint %}
| Permission | Description | Roles Example |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | No access to the **Exception Management** section on the **Server Settings** page. Users cannot view or modify the approval workflow configuration and the list of approvers. | SOC Tier 1 and Tier Analysts: No need for visibility into approval workflow configuration. |
| View | The **Exception Management** section is visible on the **Server Settings** page. Users can view the approval configuration workflow and the list of approvers (names and emails). | SOC Tier 3 Analyst and Threat Hunter: Can view the approval workflow to understand the exception approval process and whether the exceptions they encounter have been approved. |
| View/Edit | Read and write access to the **Exception Management** section on the **Server Settings** page. Users can configure the exception approval workflow and manage approvers. | Security Engineer: Full access to toggle approval requirements and manage the approvers list. |
**Required and recommended permissions**
Consider adding the following permissions:
| Permissions | Permission Level | Reason |
| -------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| General Configuration | View or View/Edit | - View: The Exception Management section is on the Server Settings page. Without this permission, users cannot view the section. Required.
- View/Edit: Users who configure exception approval workflows may also need to manage other server settings (email contacts, Google Maps key, etc.).
|
| Issue Exclusion | View | Approver administrators should understand the exclusion/exception rules they are configuring for approval workflows. Without this, they are configuring approval settings without visibility into the rules being approved. Strongly recommended. |
| Exception Management Admin | View | Understanding the exception rules that will go through the approval workflow helps configure appropriate approvers and approval requirements. Strongly recommended. |
---
# 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/exceptions-configuration-permissions/exception-approver-admin-permissions.md?ask=&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.