> 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/viewing-team-permission-sets.md).
# Viewing team permission sets
{% hint style="info" %}
**Required team permission - either:**
* Create and manage custom team and workspace permission sets
* Manage user access within the team
{% endhint %}
## Displaying the list
To display the list of team permission sets:
1. In the user menu, click **Team Settings**.
2. On the **Team Settings** view, click **Access Management**.
3. On the **Access Management** tab, click **Team Permission Sets**.
Team Permission Sets list
## Information in the list
For each team permission set, the list includes:
* The permission set name.
* Whether the permission set is built-in or custom.
* For custom permission sets, when it was most recently modified, and the user who modified it.
## Viewing the details for a permission set
To view the details for a permission set, in the permission sets list, click **Settings**.
The details panel for a permission set includes:
* The name of the permission set.
* The permission configuration.
Settings panel for a team permission set
---
# 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/viewing-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.
