> 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/permission-sets-about.md).

# About permissions and permission sets

Tonic Structural uses permissions and permission sets to manage role-based access (RBAC) to Structural features and functions.

## What is a permission?

A permission grants access to a specific feature or function.

## What is a permission set?

A permission set is a collection of permissions that can be assigned to a user or an SSO group.

* Built-in permission sets come with Structural. You cannot edit or delete a built-in permission set.
* On the Enterprise license plan, you can also create custom permission sets.

## Types of permissions and permission sets

### Global permissions and permission sets <a href="#permission-sets-about-global" id="permission-sets-about-global"></a>

Global permissions control access to features and functions that apply across an entire organization. For example, global permissions control who can configure environment settings.

For the lists of built-in global permission sets and available permissions, go to [Built-in global permission sets and available permissions](/app/structural-user-access/permissions/global-permissions/global-permission-built-in.md).

For information on how to assign global permission sets, go to [Configuring access to global permission sets](/app/structural-user-access/permissions/global-permissions/global-permission-set-access.md) and [Granting initial admin access on self-hosted instances](/app/structural-user-access/permissions/global-permissions/managing-admin-users.md).

You can also [select a default global permission set to assign to all new users](/app/structural-user-access/permissions/global-permissions/global-permission-set-default.md).

### Team permissions and permission sets

Team permissions control access to features and functions that are managed within individual teams.

For example, team permissions control who can create workspaces, configure generator presets, and configure custom sensitivity rules.

For the list of built-in team permission sets and available permissions, go to [Built-in team permissions and permission sets](/app/structural-user-access/permissions/team-permissions/built-in-team-permissions-and-permission-sets.md).

For information about how to assign team permission sets, go to [Configuring access to team permission sets](/app/structural-user-access/permissions/team-permissions/configuring-access-to-team-permission-sets.md).

You can also [select a default team permission set to assign to new team members](/app/structural-user-access/permissions/team-permissions/selecting-the-default-team-permission-set.md).

Each team manages and assigns team permission sets within their team. Each team creates their own custom team permission sets, and assigns team permission sets to their team members.

### Workspace permissions and permission sets <a href="#permission-sets-about-workspace" id="permission-sets-about-workspace"></a>

Workspace permissions provide access to specific workspace management features and functions. Workspaces are managed within a team.

Workspace permission sets are assigned to team users and groups within the context of a specific workspace. For example, a user might have the Editor permission set in one workspace and the Viewer permission set in another workspace.

For the lists of built-in workspace permission sets and available permissions, go to [Built-in workspace permission sets and available permissions](/app/structural-user-access/permissions/workspace-permissions/workspace-permission-built-in.md).

For information on how to assign workspace permission sets, go to [Sharing workspace access](/app/workspace/workspace-access-management/workspace-sharing.md).

You can also [select a default workspace permission set to assign to workspace owners](/app/structural-user-access/permissions/workspace-permissions/workspace-owner-permission-set.md).


---

# 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/permission-sets-about.md?ask=<question>&goal=<user_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.