> 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/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-access-control-configuration/limit-access-to-investigations-using-rbac.md).

# Limit Access to Investigations using RBAC

Limit Cortex XSOAR 6.15 investigation access with role-based controls.

You can limit access to the investigations using RBAC by either assigning a specific role to the incident (read and write access to the investigation) or by assigning a role with read-only permission. This procedure uses the **`incident_set`** command to limit investigation permissions, but you can also add the **`Role`** and **XSOAR Read Only** rules fields to the Incident Summary page when customizing incident layouts. You can also add these columns to the Incidents table in the Incidents page.

1. In the **Incident** page, select the incident you want to restrict access.
2. Restrict the incident to a role.
   1. In the CLI, type the following command:

      `/incident_set roles=`*`<select role>`*
   2. To check that the role was assigned to the incident, click the War Room tab.
3. Restrict the incident to a read-only role.
   1. In the CLI, type the following command:

      `!setIncident xsoarReadOnlyRoles=`*`<select role>`*
   2. To check that the role was assigned to the incident, click the War Room tab.
4. (Optional) For automations:
   * Use the `setIncident` command in a playbook.
   * Specify the roles that you want to have access to the incident investigation.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-access-control-configuration/limit-access-to-investigations-using-rbac.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 `build a script that syncs our docs to a CMS` 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.