> 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/search-permissions-1/forensics-permissions.md).

# Forensics permissions

Configure permissions for forensics.

Controls access to Forensics (**Investigation & Response** → **Forensics**). Forensic investigations streamline your case response, data collection, threat hunting, and analysis of your endpoints.

{% hint style="info" %}

### License

You need the Forensics add-on to view Forensic investigations.
{% endhint %}

For more information, see [Forensic investigations](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/forensics/forensic-investigations.md).

| Permission | Description                                                                                                           | Roles Example                                                                                                                                                                                                                                                                                 |
| ---------- | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None       | Users cannot see forensic artifacts or trigger new collections.                                                       |                                                                                                                                                                                                                                                                                               |
| View       | Read-only access to forensics investigations                                                                          | <ul><li>SOC Tier-1 Analyst: View forensics data for context, but cannot initiate collections.</li><li>SOC Tier-2 Analyst: View forensics data and escalate to Tier-3 for collections.</li><li>Security Engineer: View forensics for understanding data as not the primary function.</li></ul> |
| View/Edit  | Full read and write access, including create, edit, and delete investigations, start, pause, and delete threat hunts. | <ul><li>SOC Tier-3 Analyst: Full forensics capabilities, including triage and hunt.</li><li>Threat Hunter: Full forensics for deep-dive investigations.</li></ul>                                                                                                                             |

**Required and recommended Permissions**

Consider adding the following permissions:

| Permission            | Permission Level | Reason                                                                                                                                                       |
| --------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Agent Administrations | View             | Forensics displays endpoint data extensively. Without this, endpoint information within forensics investigations will fail to load or show errors. Required. |
| Query Center          | View             | Strongly recommended to run queries on the host data.                                                                                                        |
| Cases & Issues        | View             | Strongly recommended to view issues associated with forensic investigations.                                                                                 |


---

# 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/search-permissions-1/forensics-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.