> For the complete documentation index, see [llms.txt](https://docs.pipekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pipekit.io/organizations-and-access/basic-permissions.md).

# Basic Permissions

Grant organization-wide permissions to users and groups when your organization uses basic permissions.

{% hint style="info" %}
This page applies when your organization uses basic permissions, the default for every organization. If you see a workspace switcher in the navigation bar, or an `Enforcing policy` banner on the `Users` tab, read [Multi-tenant RBAC](https://docs.pipekit.io/organizations-and-access/rbac.md) instead.
{% endhint %}

Basic permissions apply to the whole organization. You grant them per user on the `Users` tab, or per group on the `Groups` tab.

## Permissions

| Permission | What it allows                                                                                                                                                                                                             |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `read`     | View pipes, runs, logs, metrics, templates, clusters, secret environments, alert rules, alert providers, registry credentials, Git accounts, and pending invitations                                                       |
| `create`   | Create pipes and templates, run pipes and submit workflows, and add secrets, secret environments, run conditions, alert providers, alert rules, Git accounts, and registry credentials                                     |
| `update`   | Edit pipes, templates, secrets, and run conditions, stop and resubmit runs, suspend and resume cron workflows, rotate deploy keys, and change or disconnect Git accounts                                                   |
| `delete`   | Delete pipes, templates, workflows, secrets, secret environments, run conditions, alert rules, alert providers, registry credentials, and pending invitations                                                              |
| `admin`    | Every other permission, plus adding, changing, and deleting clusters, organization settings, inviting users and changing their permissions, groups, SSO and SCIM, Git mappings, config as code, and Bring Your Own Logging |

For examples of the permission an action needs, refer to the "Who can" sections on these pages:

* [Who can manage users](https://docs.pipekit.io/organizations-and-access/members.md#who-can-manage-users)
* [Who can change settings](https://docs.pipekit.io/organizations-and-access/settings.md#who-can-change-settings)
* [Who can manage clusters](https://docs.pipekit.io/using-pipekit/clusters.md#who-can-manage-clusters)
* [Who can act on runs and nodes](https://docs.pipekit.io/using-pipekit/runs/inspect.md#who-can-act-on-runs-and-nodes)

## Grant permissions to a user

1. Open the `Org` page, go to `People & Access`, and open `Users`.
2. Find the user and click the gear icon on the right-hand side.
3. Choose `Edit Permissions`.
4. Select the permissions to grant, and save.

If your organization provisions users through SCIM, `Edit Permissions` is not shown. Set the permission level on the group instead.

## Grant permissions to a group

Groups come from your identity provider. Your identity provider either syncs groups through SCIM, or sends them each time a user signs in. In an organization that uses SCIM, groups come only from SCIM. When groups arrive at sign-in, each sign-in replaces the user's groups. If your identity provider no longer lists a group for the user, the user loses the access that group gave. For setup, refer to [Okta](https://docs.pipekit.io/organizations-and-access/sso/okta.md) and [Microsoft Entra](https://docs.pipekit.io/organizations-and-access/sso/entra.md).

1. Open the `Org` page, go to `People & Access`, and open `Groups`.
2. Click the cog on the group.
3. Select a different permission level.

Once a user belongs to any group, Pipekit uses only the permissions of their groups. Permissions set on that user directly no longer count.

{% hint style="warning" %}
Pipekit gives every group your identity provider syncs the `admin` permission by default. Lower the permission level of each group after it appears on the `Groups` tab. A group that arrives when a user signs in starts with no permissions.
{% endhint %}

## Moving to multi-tenant RBAC

Multi-tenant RBAC splits your organization into workspaces, so each team sees only its own pipes, runs, and templates. Consider it when teams need separate access, or when you want to manage access as code. Ask your Pipekit account contact or email `hello@pipekit.io`. For how the two systems compare, refer to [Access Control](https://docs.pipekit.io/concepts/access-control.md).
