> 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/app/structural-user-access/permissions/team-permissions/configuring-custom-team-permission-sets.md).
# Configuring custom team permission sets
{% hint style="info" %}
**Required team permission:** Create and manage custom team and workspace permission sets
{% endhint %}
You can create custom team permission sets. A custom permission set allows you to have more precise control over team permissions.
## Creating a custom team permission set
To create a custom team permission set:
1. On the **Team Permission Sets** list, click **Create Team Permission Set**.
Create Team Permission Set panel to add a custom team permission set
2. On the permission set details panel, in the **Name** field, provide a name for the permission set.\
\
Permission set names must be unique.
3. To base the permission set on an existing permission set, from **Create from existing permission set**, select the existing permission set to use.\
\
When you base the permission set on an existing permission set, Structural copies the permissions from the existing permission set to the new permission set. You can then update the selected permissions as needed.\
\
For example, you might want to create a team permission set that is nearly identical to the built-in Team Admin permission set, but that removes the option to manage team membership. You can base the new permission set on the Team Admin permission set, then remove the team membership permission. \
\
After you save the new permission set, it is not connected to the permission set that you used to obtain the initial set of permissions.
4. Select the 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.
5. To save the new permission set, click **Save**.
6. Structural prompts you to configure access to the new permission set.\
\
To display the access management panel for the permission set, click **Manage User Access**.\
\
To not manage access at that time, click **Skip**.
## Editing a custom team permission set
You cannot make any changes to a built-in permission set.
For a custom permission set, you can change the permission set name and adjust the assigned permissions.
To edit an existing custom permission set:
1. On the **Team Permission Sets** list, click **Settings**.
2. On the permission set details panel, update the permission set configuration.
3. Click **Save**.
## Deleting a custom team permission set
You can delete a custom permission set. You cannot delete a built-in permission set.
You cannot delete a 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 permission set:
1. On the **Team Permission Sets** list, click **Settings**.
2. On the permission set details panel, click **Delete Permission Set**.
Delete Permission Set option on the settings panel for a custom team permission set
2. 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 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/app/structural-user-access/permissions/team-permissions/configuring-custom-team-permission-sets.md?ask=&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.
