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 navigation bar, click Workspace settings or Organization settings > Members.
-
In the table, under Workspace role, click the current role and then select a new role.
-
You can't demote admins.
-
If you're assigning roles in a workspace, you can't assign a role that's more restricted than the role that person holds in the organization. For example, an organization admin must also be a workspace admin. However, an organization reader can be a workspace reader, editor, or admin.
-