> 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/investigation-and-response-permissions/automation-permissions-1/automation-exclusion-center-permissions.md).

# Automation Exclusion Center permissions

Configure permissions for Automation Exclusion Center.

Controls access to the Automation Exclusion Center (**Settings** → **Configurations** → **Automation** → **Automation Exclusion Center**), which prevents a command or script from a remediation action. For more information, see [Automation Exclusion Center](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/automation-exclusion-center.md).

| Permission | Description                                                                                                                                           | Roles Example                                                                                          |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| None       | Cannot access the Automation Exclusion Center, view any exclusion policies, or view excluded assets.                                                  | SOC Tier 1: Do not need to view exclusion policies or excluded assets.                                 |
| View       | Can access the Automation Exclusion Center (read-only), view exclusion policies, excluded assets and counts, and view policy compliance status.       | SOC Tier 2 and 3 Analysts and Threat Hunters: Need View access to help understand automation behavior. |
| View/Edit  | All View capabilities, plus create new exclusion policies, edit existing policies, delete policies, manage asset exclusions, and update policy rules. | Security Engineers: Need to configure automation behavior and permissions.                             |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission     | Permission Level  | Reason                                                                                                                                             |
| -------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Playbooks      | Enabled           | Strongly recommended to understand which playbooks are impacted by exclusions.                                                                     |
| Scripts        | Enabled           | Strongly recommended for Playbooks; exclusions may reference scripts.                                                                              |
| Cases & Issues | View or View/Edit | Exclusions applied to cases (need context). View/Edit Recommended to trigger playbooks. Helps manage exclusions effectively. 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/automation-permissions-1/automation-exclusion-center-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.