Skip to main content

User Roles

Learn about Crux authorizations and Role Based Access Control

Jon Tam avatar
Written by Jon Tam
Updated over 4 months ago

A Role binds a user to a set of permissions and an access policy, controlling what the user is allowed to perform in relation to data products, connections, other users, and organizational settings within the organization they are part of. A Role defines a collection of permissions controlling access and operations applicable to data products, connections, users, groups, other roles, organizations, and system-wide settings.


Overview

Crux supports the following pre-defined roles: Viewer, Editor, and Admin.


Viewer

A user with the Viewer role has read-only access to all current and future data products, connections, or system settings. This is the default role assignment for the new users in the organization.

A Viewer's access includes:

  • A Viewer has read-only access to the data products and connections already available in the system.

  • A Viewer cannot create new data products or make changes to data products already in the system.

  • A Viewer cannot create new source and destination connections.

  • A Viewer cannot perform actions impacting the organization or other users. For example, they cannot change roles for themselves or their colleagues, invite new users to the platform, or make changes to the organization-wide settings, such as notification policies.


Editor

Editor’s access includes managing all current and future data products and connections.

An Editor's access includes all entitlements of a Viewer, plus:

  • An Editor can create, modify, and delete notification rules and distribution channels to stay informed about the health and quality of data products.

  • An Editor cannot perform actions impacting the organization or other users. For example, they cannot change roles for themselves or their colleagues, invite new users to the platform, or make changes to the organization-wide settings.


Admin

An Admin has full administrative privileges over the organization they belong to. In addition to having all the privileges of an Editor or Security Admin, an Admin has permission to make system-wide changes impacting their entire organization and other users.

An Admin’s access includes all entitlements of a Viewer and an Editor, plus:

  • An Admin can invite new users to the system, change user role assignments, reset passwords, activate and deactivate users, or delete users permanently.

  • An Admin can make changes to any organization-wide administrative settings.


Role definitions

The table below describes the capabilities and access control of each role:

Viewer

Editor

Admin

Crux Catalog

Browse, search, and filter data products and suppliers

Request access to data products

Data Products

View data products

Users

View user profiles

Invite new users

Modify user roles

Delete users (cannot delete the last Admin)

Monitors and Notifications

Configure (create, edit, delete) notification rules

Configure (create, edit, delete) distribution channels

Organization

Make changes impacting the organization

Did this answer your question?