> 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/selecting-the-default-team-permission-set.md).
# Selecting the default team permission set
{% hint style="info" %}
**Required team permission:** Manage user access within the team
{% endhint %}
By default, all new team members are assigned the built-in Team Member team permission set.
You can also configure a different team permission set to assign to team members.
The permission set cannot be removed.
When you choose a different permission set to assign to all users, unless they were otherwise assigned the previous default permission set, they lose access to it.
To set the default team permission set to assign to all team members:
1. In the user menu, click **Team Settings**.
2. On **Team Settings** view, click **Access Management**, then click **Team Permission Sets**.
3. On the **Team Permission Sets** list, the current permission set for all users is marked as **Assigned to all members**.\
\
To select a different permission set, hover over the permission set row, then click **Assign to all members**.
Selecting a different team permission set to assign to all team members
4. The confirmation panel explains the risks of making this change.\
\
To confirm the change:
1. Check **I have read and understand the risks**.
2. 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/selecting-the-default-team-permission-set.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.
