> 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/restrict-an-investigation.md).

# Restrict an Investigation

Restrict access to Cortex XSOAR 6.15 investigations.

You can restrict an investigation to the incident owner and the team associated with the investigation.

1. Do one of the following:
   * Open the incident and select Actions → Restrict incident.

     To remove the restriction, select Actions → Permit incident.
   * In the CLI, type ` /investigation_restrict id=`` `` `*`id_ number`*
2. (Optional) For Automation, do the following:
   * Use the `restrictInvestigation` command in a playbook.
   * Specify the incident ID of the incident for which you want to restrict access.
   * Set the `Restrict` argument to `True` to restrict the incident.
   * Set the `Restrict` argument to `False` to remove restricted from the incident.


---

# 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/restrict-an-investigation.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.