> 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.md). # Team permissions Team permissions control access to features that are managed within a team and are outside the context of a specific workspace. ## View and configure team permission sets


Built-in permission sets and permissions Team permission sets that come with Structural and available team permissions.	Built-in team permissions and permission sets
View team permission sets Display the list of team permission sets and view permission set details.	Viewing team permission sets
Configure custom team permission sets Create your own team permission sets with a set of permissions that you select.	Configuring custom team permission sets

## Configure team permission set access


Select the default team permission set Identify the team permission to grant to all new team members.	Selecting the default team permission set
Configure team permission access Assign users and SSO groups to team permission sets.	Configuring access to team permission sets

--- # 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.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.