Role-based access control (RBAC)

CoreStandardPlusProEnterprise Flex Compare

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.

Organization roles

When you assign an organization role, Airbyte scopes permissions to the entire organization, which includes all workspaces in that organization.

Permissions	Member	Reader	Runner	Editor	Admin
Read Organization Read individual organizations	X	X	X	X	X
Create Workspace Create new workspace within a specified organization Delete a workspace				X	X
Update Organization Modify organization settings, including billing, PbA, SSO Modify user roles within the organization					X

Workspace roles

In a workspace role, Airbyte scopes permissions to that specific workspace. You can override an organization role by assigning someone a higher role in a workspace. However, 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.

Permissions	Reader	Runner	Source editor	Destination editor	Editor	Admin
Read Workspace List the connections in a workspace Read individual connections Read workspace settings (data residency, users, connector versions, notification settings)	X	X	X	X	X	X
Sync Connection Start/cancel syncs and refreshes		X	X	X	X	X
Modify Source Settings Create, modify, delete sources in a workspace Run the OAuth flow for a source Create/Update/Delete connector builder connectors			X		X	X
Modify Destination Settings Create, modify, delete destinations in a workspace Run the OAuth flow for a destination				X	X	X
Update Connection Modify a connection, including name, replication settings, normalization, DBT Clear connection data Create/Delete a connection			X	X	X	X
Update Workspace Update workspace settings (data residency, users, connector versions, notification settings) Modify workspace connector versions						X

Source editor and destination editor

Destinations are usually the more critical half of a pipeline. They're shared warehouses and lakes that a central platform team owns, and a careless configuration change there affects everyone using them. Source editor exists so that the teams who know their own source systems can connect them and start syncing without waiting on the platform team, and without being able to reconfigure the destinations they write to. Give destination editor to the people who do own those destinations.

Both roles can create and modify connections, and both can run syncs. Neither role can change workspace settings, and neither one implies the other. If someone needs to manage both sources and destinations, give them the editor role instead.

Best practices for assigning roles

• At the organization level, assign the lowest level of permission necessary.
• At the workspace level, assign higher roles for individual workspaces as needed to override organization role within that workspace.
• Don't assign admin roles frivolously. Once someone is an admin, you can't demote them.

Setting roles

1. In the navigation bar, click Workspace settings or Organization settings > Members.

2. In the table, under Workspace role, click the current role and then select a new role.