> 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/concepts/access-control.md).

# Access Control

Pipekit has two permission systems, basic permissions and multi-tenant RBAC. Find out which one your organization uses and where to read more.

Access control decides who can see, run, and manage workflows in your organization. Pipekit enforces it at the Pipekit API and UI.

Pipekit has two permission systems. Your organization uses one of them at a time.

|                      | Basic permissions                                              | Multi-tenant RBAC                                             |
| -------------------- | -------------------------------------------------------------- | ------------------------------------------------------------- |
| Who has it           | Every organization, by default                                 | Organizations that switch to it with Pipekit                  |
| Where you set access | Per user on the `Users` tab, and per group on the `Groups` tab | In an RBAC policy file that you publish                       |
| What access covers   | The whole organization                                         | One workspace, or every workspace with an org-scope binding   |
| What you grant       | Permissions: read, create, update, delete, and admin           | Roles: Org Admin, Workspace Admin, Editor, Runner, and Viewer |

## Which one does your organization use?

Your organization uses multi-tenant RBAC if you see either of these:

* A workspace switcher in the navigation bar. Every user who can reach a workspace sees it.
* An `Enforcing policy` banner on the `Users` tab under `People & Access`. Only an Org Admin can open that tab under multi-tenant RBAC.

If you see `You don't have access to any workspaces yet`, your organization uses multi-tenant RBAC and you can reach no workspace. Ask your Org Admin to add you to a workspace.

If you see none of these, your organization uses basic permissions.

## Switching to multi-tenant RBAC

To use multi-tenant RBAC, get in touch with your Pipekit contact or email `hello@pipekit.io`.

## Read more

* [Basic Permissions](https://docs.pipekit.io/organizations-and-access/basic-permissions.md): what each permission allows and how to grant it.
* [Multi-tenant RBAC](https://docs.pipekit.io/organizations-and-access/rbac.md): workspaces, roles, bindings, and the permission reference.
* [Set Up Multi-tenant RBAC](https://docs.pipekit.io/organizations-and-access/rbac/set-up.md): the steps to switch your organization.
* [Workspaces](https://docs.pipekit.io/using-pipekit/workspaces.md): how you switch between workspaces and find your work under multi-tenant RBAC.
