> 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/reference-and-developer-docs/role-based-access-control/configuration-permissions/dataset-management-permissions.md).

# Dataset Management permissions

Manage access to Cortex XDR dataset-level configurations and object sharing.

Controls whether a user can access the **Dataset Management** page and interact with user-managed datasets (User, Lookup, Dataset Views, and Correlation) through **Settings** → **Configurations** → **Data Management** → **Dataset Management**.

This permission uses a **Disabled**/**Enabled** model. When **Enabled**, additional capabilities appear as checkboxes to further refine what the user can do:

* **Create Datasets**: Enables the **+ Lookup** and **New Dataset View** buttons, allowing the user to create new user-managed datasets. The user who performs this action becomes the **Owner** and is granted the inherent right to edit, delete, and manage sharing for that specific object. By default, newly created datasets are assigned an initial access state (**Restricted** or **Public**) based on your tenant-level access settings.
* **Edit Public Datasets**: Allows the user to modify (append or overwrite) custom datasets set to **Public**, even if they are not the owner.

| Permission | Description                                                                                                                                                | Roles Example                                                                                                             |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Disabled   | Users cannot navigate to the **Dataset Management** page or view datasets they do not own or that have not been shared with them.                          | **SOC Tier-1 Analyst**: Typically only requires querying pre-defined datasets rather than managing the collection itself. |
| Enabled    | Grants access to the **Dataset Management** page. Visibility of specific datasets is then determined by per-object permissions (Owner, Editor, or Viewer). | **SOC Tier-2/3 Analyst**: May need to understand data schemas or manage specific lookup tables during investigations.     |

**Required and recommended permissions**

Consider adding the following permissions to complement dataset management:

| Permission      | Permission Level | Reason                                                                                             |
| --------------- | ---------------- | -------------------------------------------------------------------------------------------------- |
| XQL Search      | Enabled          | Required to run queries against managed datasets and use the `target` command.                     |
| Data Management | View/Edit        | Required if the user also needs to manage ingestion pipelines, parsing rules, or data model rules. |
| Query Library   | Enabled          | Allows users to save and share complex queries that target specific managed datasets.              |


---

# 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/reference-and-developer-docs/role-based-access-control/configuration-permissions/dataset-management-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.