> 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/built-in-team-permissions-and-permission-sets.md). # Built-in team permissions and permission sets Team permissions and permission sets control access to resources within a specific team. ## Built-in team permission sets Structural comes with the following built-in team permission sets. ### Team Member Allows users to create workspaces. To enable users to share workspace access with other team members, they are automatically permitted to find other team members. ### Team Admin Provides full access to all team permissions. ## Available team permissions The following tables list the available team permissions, and indicate how the permissions apply to the built-in team permission sets. ### User management permissions

Permission	Team Member	Team Admin
View team users	✔️	✔️
Create and manage custom team and workspace permission sets		✔️
Manage user access within the team		✔️

### Workspace management permissions

Permission	Team Member	Team Admin
Create workspaces	✔️	✔️
Copy any workspace in the team		✔️

### Configuration management permissions

Permission	Team Member	Team Admin
Configure and manage generator presets		✔️
Manage sensitivity rules		✔️
Manage secrets managers		✔️

### Team administration permissions

Permission	Team Member	Team Admin
Enable diagnostic logging and uploading logs directly to Tonic.ai		✔️

--- # 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/built-in-team-permissions-and-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.