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

# Graph Search permissions

Configure permissions for Graph Search.

Limits access to Graph Search **Investigation & Response** → **Search** → **Query Builder** → **Graph Search)**, which enables visual exploration of cloud asset relationships, configurations, and security findings through an interactive graph interface, such as discovering cloud asset relationships, investigating security findings, and analyzing effective permissions.

{% hint style="info" %}

### License

Graph Search requires a Cloud Posture Security, Cloud Runtime Security, or Cortex XDR Premium license.
{% endhint %}

For more information, see [Graph Search](/cortex-xdr-5.x/reference-and-developer-docs/graph-search/what-is-graph-search.md).

| Permission   | Description                                                                                                                              | Roles Example                                                                                                                                                                                                                                             |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Graph Search | Cannot view the **Graph Search** page, execute graph queries, or view saved queries.                                                     |                                                                                                                                                                                                                                                           |
| View         | Execute graph queries, export, and support all view capabilities, such as viewing recent queries, graph definitions, and runtime events. |                                                                                                                                                                                                                                                           |
| View/Edit    | Full access to use the graph and save specific graph views or templates for others to use.                                               | <ul><li>SOC Tier-1, 2, and 3 Analysts: Save graph queries for reuse in investigations.</li><li>Threat Hunter: Full graph search for cloud threat hunting.</li><li>Security Engineer: Full graph search for cloud security engineering/IT Admin.</li></ul> |

**Required and recommended Permissions**

Consider adding the following permissions:

| Permission            | Permission Level                 | Reason                                                                                                                                                           |
| --------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Query Center          | View                             | Graph Search translates XQL logic into visual nodes. Without search permissions, the graph cannot query the data lake. Required.                                 |
| Query Library         | Enabled with checkboxes selected | Strongly recommended to view and save graph queries in the library tab. Without this, the library tab in the Graph Search side panel may not function correctly. |
| Agent Administrations | View                             | Recommended to populate host-specific metadata (like OS version or isolation status) within the graph nodes.                                                     |
| Asset Inventory       | View                             | Graph Search visualizes cloud asset data. Required to view asset data in the graph search. Required.                                                             |
| Cases & Issues        | View                             | Strongly recommended to view cases and issues in graph search.                                                                                                   |
| Action Center         | View/Edit                        | Recommended so an analyst can right-click a node (process or file) in the graph and take immediate action, such as Terminate Process.                            |


---

# 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/graph-search-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.