> 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/configuration-permissions/external-issues-mapping-permissions.md).

# External Issues Mapping permissions

Manage access to Cortex XSIAM mappings for external issue integrations.

Configure how alerts from third-party systems are translated into Cases through **Settings** → **Configurations** → **Data Collection** → **External Issues Mapping**.

For more information, see [External alerts using External Issue Mapping](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/external-alerts-using-external-issue-mapping.md).

| Permission | Description                                                                                                                                                                                                                                                                                                                        | Roles Example                                                                                                                                                                   |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | Users cannot access the **External Issue Mapping** page.                                                                                                                                                                                                                                                                           | SOC Tier-1 Analyst: External mapping configuration is not within Tier-1 scope.                                                                                                  |
| View       | Users can access the **External Issue Mapping** page and view all configured issue mappings and parsers. They can review how external alerts from third-party systems (such as Splunk, QRadar, or other SIEMs) are being mapped to issue fields. They can examine parser configurations, field mappings, and transformation rules. | <ul><li>SOC Tier 2 and 3 Analysts: Can review mappings for investigation purposes.</li><li>Threat Hunter: Understanding issue sources is valuable for threat hunting.</li></ul> |
| View/Edit  | Users have full control over external issue mapping configurations. They can create new parsers and mapping rules, modify existing field mappings and transformation logic, enable or disable specific mappings, configure how external issue fields map to issue properties, and delete mapping configurations.                   | Security Engineer: Responsible for configuring alert mappings and parsers.                                                                                                      |

### Required and recommended permissions

Consider adding the following permissions:

| Permission      | Permission Level | Reason                                                                              |
| --------------- | ---------------- | ----------------------------------------------------------------------------------- |
| Cases & Issues  | View             | View the issues that result from external mappings. Required.                       |
| Detection Rules | View             | Understanding correlation rules that may use external issues. Strongly Recommended. |
| Data Sources    | View             | Understanding which data sources feed into external issue mappings. 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-xsiam/reference-and-developer-docs/role-based-access-control/configuration-permissions/external-issues-mapping-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.