Roles and permissions

Roles and permissions determine a member's access to the functionalities and assets. Recurve uses a two-tier access model with predefined roles:

  • Organization level: controls who can manage company-wide resources like team members, billing, and environment setup.

  • Project level: determines what specific actions members can perform within individual projects, such as viewing data, performing transformation, or managing project resources.

Each member can have different roles across the organization and its projects.

Organization level

  • Owner: has access to all dashboards and resources.

  • Admin: can view and edit all configuration dashboards and resources, including environment setup, projects, and users.

  • Member: can only view dashboards and have limited access to resources.

Permissions
Owner
Admin
Member

View organization information

Edit organization information

Create, edit, and delete deparments and users

View worker list

Deploy, join, start, stop, remove workers

Generate API keys

View destinations

Add, edit, delete destinations

View integration list

Add, edit, remove integrations

View project list

Create project

Delete project

✓ (as project owner)

✓ (as project owner)

Project level

  • Admin: can view and edit all configuration dashboards and resources of the project.

  • Developer: can view and edit assets.

  • Viewer: can view assets only.

Permissions
Admin
Developer
Viewer

View library assets (variables, macros, generic tests)

Edit library assets

View packages and depedencies

Configure packages and depedencies

View data design assets (sources, models, pipelines)

Edit data design assets

View lineage

Preview and build design data assets

View metadata

Edit metadata

View Pipeline Health dashboard

Edit pipeline jobs

View Data Quality dashboard

View project settings

Configure project connections

Edit project members

Last updated