> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-permissions/dataset-permissions/dataset-permission-sets-custom.md).

# Configuring custom dataset permission sets

{% hint style="info" %}
**Required global permission:** Manage custom permission sets
{% endhint %}

You can create custom dataset permission sets.

A custom permission set allows you to have more precise control over dataset permissions.

For example, you might want a dataset permission set that allows a user to manage the files but not share or delete the dataset.

## Creating a custom dataset permission set <a href="#custom-permission-set-create" id="custom-permission-set-create"></a>

To create a custom dataset permission set:

1. On the **Dataset Permission Sets** list, click **Create Custom Dataset Permission Set**.
2. On the permission set details panel, in the **Permission Set Name** field, type the name for the new permission set.\
   \
   Each dataset permission set must have a unique name.
3. Select the dataset permissions to grant to the permission set.\
   \
   If a permission checkbox is checked, then the permission is granted to the permission set.\
   \
   If a permission checkbox is not checked, then the permission is not granted to the permission set.
4. To save the new dataset permission set, click **Save**.

## Editing a custom dataset permission set <a href="#custom-permission-set-edit" id="custom-permission-set-edit"></a>

You cannot make any changes to a built-in dataset permission set.

For a custom dataset permission set, you can change the permission set name and adjust the assigned permissions.

To edit an existing dataset custom permission set:

1. On the **Dataset Permission Sets** list, click **Settings**.
2. On the permission set details panel, update the permission set configuration.
3. Click **Save**.

## Deleting a custom dataset permission set <a href="#custom-permission-set-delete" id="custom-permission-set-delete"></a>

You can delete a custom dataset permission set. You cannot delete a built-in dataset permission set.

You cannot delete a dataset permission set that is assigned to any users or groups. Before you can delete the permission set, you must remove the assignment.

To delete a custom dataset permission set:

1. On the **Dataset Permission Sets** list, click **Settings**.
2. On the permission set details panel, click **Delete Permission Set**.
3. On the confirmation panel, click **Confirm**.


---

# 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://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-permissions/dataset-permissions/dataset-permission-sets-custom.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.