> 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/admin/tonic-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 are outside of the context of a specific workspace. For example, global permissions control who can manage users and 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/admin/tonic-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/admin/tonic-user-access/permissions/global-permissions/global-permission-set-access.md) and [Granting initial admin access on self-hosted instances](/app/admin/tonic-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/admin/tonic-user-access/permissions/global-permissions/global-permission-set-default.md).

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

Workspace permission sets are assigned to 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/admin/tonic-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/admin/tonic-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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tonic.ai/app/admin/tonic-user-access/permissions/permission-sets-about.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
