Skip to content
ricochet

User Roles

Every user has one of three roles. The role sets what the user can do across the whole server.

  • Admin: can manage users and all server content
  • Developer: can deploy items
  • Consumer: can only view items
Capability Admin Developer Consumer
View internal items ✅ ✅ ✅
View external items ✅ ✅ ✅
Deploy content ✅ ✅ ❌
Manage own items ✅ ✅ ❌
Access all items ✅ ❌ ❌
Manage server ✅ ❌ ❌
Assign user roles ✅ ❌ ❌

New users get a default role the first time they sign in. The default role is Developer, but you can change it to fit your team.

Add this to your ricochet-config.toml:

[auth]
default_role = "consumer"

Admins have full access to all actions in the ricochet UI. They can:

  • Manage all content items on the server
  • Manage all users and their roles
  • Access all deployed items, whatever their access settings

Developers create and manage their own content. They can:

  • Deploy items to ricochet using the CLI or Git
  • Manage settings for items they own
  • Work on items they are invited to
  • View internal and external items they own or work on as collaborators

Developers cannot:

  • Access other users’ private items (unless added as a collaborator)
  • Manage server settings
  • Assign user roles

Consumers can only view items:

  • They can view items they have access to
  • They cannot deploy or change any items
  • They cannot open private items unless added as a collaborator

The Consumer role suits:

  • Stakeholders who need to view dashboards and reports
  • External users accessing public content
  • Teams that consume data products without creating them

Admins assign user roles in the ricochet admin UI.

Initial Login: When users first sign in through OIDC, ricochet gives them the default role from your config.

Changing Roles: Admins open the Users page at /users, select the user, and change their Role.