Role Based Access Control (RBAC)
Role Based Access Control allows a user with Administrative access to apply roles to users, granting different levels of permission within an Organization or Workspace.
Self-Managed Enterprise instances have an Instance Admin
role in addition to the other roles outlined in this document. The first user who logs on to Airbyte in a Self-Managed Enterprise instance will be assigned this role. This user will have all permissions listed below for all workspaces and all organizations associated with their Enterprise account. To update this assignment, enterprise customers should contact Airbyte support.
Organization Resource Roles
Permissions are scoped to the given Organization for which the user has this role, and any Workspaces within.
Permissions | Member | Reader | Runner | Editor | Admin |
---|---|---|---|---|---|
Read Organization
| X | X | X | X | X |
Create Workspace
| X | X | |||
Update Organization
| X |
Workspace Resource Roles
Permissions are scoped to the specific Workspace in which the user has this role.
Permissions | Reader | Runner | Editor | Admin |
---|---|---|---|---|
Read Workspace
| X | X | X | X |
Sync Connection
| X | X | X | |
Modify Connector Settings
| X | X | ||
Update Connection
| X | X | ||
Update Workspace
| X |
Setting Roles
In the UI, navigate to Settings
> General
to see a list of your Organization or Workspace members. Here, by selecting the role listed under Organization Role
or Workspace Role
, you can change the assignment.
Note that it is not possible to assign a Workspace member to a role that is more restricted than the role they've been assigned at the Organizational level.
For example, a person who is assigned to be an Organization Admin
would automatically have Admin-level permissions in all Workspaces within the Organization and can not be demoted within a Workspace. On the other hand, a person assigned to the Reader
role in an Organization could be assigned the Reader
, Editor
, or Admin
role in an individual Workspace.