> 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/configuration-permissions/object-setup-permissions/sync-profile-permissions.md).

# Sync Profile permissions

Controls access to case mirroring profiles configuration in **Settings** → **Configurations** → **Object Setup** → **Issues** → **Sync Profiles**.

Sync Profiles define the parameters for case mirroring with third-party platforms such as Jira and ServiceNow. When a profile is active, updates to cases in the tenant are automatically reflected in the external system, and depending on the profile type (inbound or bidirectional), changes in the external system can update XDR cases.

For more information, see [Create a sync profile](/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/create-a-sync-profile.md).

| Permission | Description                                                                                          | Roles Example                                                                                                                                                                           |
| ---------- | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | No access to Sync Profiles. Users cannot view, create, or select profiles for use in automation.     | <ul><li>SOC Tier 1 and 2 Analyst: Mirroring configuration is typically handled by engineers.</li><li>Threat Hunter: Layout configuration is outside the threat hunting scope.</li></ul> |
| View       | Read-only access. Users can view the Sync Profiles table and open profile details in read-only mode. | SOC Tier-3 Analyst: Should understand mirroring configurations for escalation workflows and cross-system case tracking.                                                                 |
| View/Edit  | Full read/write access to view, create, edit, and delete sync profiles.                              | Security Engineer: Configures and manages mirroring with external ticketing systems (Jira, ServiceNow).                                                                                 |

### Required and recommended permissions

Consider adding the following permissions:

| Permission       | Permission Level  | Reason                                                                                                                                                                                                          |
| ---------------- | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Integrations     | View or View/Edit | <ul><li>View: Required to view the connector integrations (Jira, ServiceNow) used by sync profiles.</li><li>View/Edit: Strongly recommended to configure the connector instances needed for mirroring</li></ul> |
| Cases & Issues   | View              | Required to view cases that use sync profiles for mirroring.                                                                                                                                                    |
| Fields and Types | View              | Strongly recommended to understand field mappings in sync profiles (which XSIAM fields map to external fields).                                                                                                 |
| Case Properties  | View              | Strongly recommended to understand the custom statuses that are mapped in sync profiles.                                                                                                                        |
| Credentials      | View              | Strongly recommended to view credentials used by connector integrations.                                                                                                                                        |
| Playbooks        | Enabled           | Recommended to configure mirroring playbooks that use sync profiles.                                                                                                                                            |
| Audit            | View              | Recommended to track sync profile changes.                                                                                                                                                                      |


---

# 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-xdr-5.x/reference-and-developer-docs/role-based-access-control/configuration-permissions/object-setup-permissions/sync-profile-permissions.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.