Console Guides

Roles

Roles configures your project's end-user multi-role system — custom roles like customer, driver, or support with their own collection permissions, separate from the built-in Owner/Admin/Developer/ Viewer roles under Team.

Find it

Roles is in the sidebar under the Access group.

Roles page with multi-role settings, the roles table, and Add custom role button marked
Roles — multi-role settings above, the role list below
  1. Click + Add custom role to define a new role.
  2. Enable multi-role turns the whole system on for this project. Allow multiple roles lets one end user hold more than one role at once; Require approval means a new signup into a role sits pending until an admin approves it, instead of activating immediately.
  3. Default role is what a new end user gets if they sign up without explicitly requesting one. Click Save settings after changing any of these.
  4. Click Edit on any row to change its permissions or hierarchy.

Add a custom role

Add custom role dialog with slug, name, description, collection permissions, and Create button marked
Add custom role dialog
  1. The slug is the stable, API-facing identifier for this role — lowercase, no spaces (e.g. rider_support).
  2. The display name shown throughout the console.
  3. A short description of who this role is for.
  4. Pick a collection, then tick Read/Create/Update/Delete to grant this role access to it.
  5. Click + Add another collection to repeat the row for as many collections as this role needs — permissions are additive across rows, and each row can be removed independently once there's more than one.
  6. Click Create once the role's permissions look right.
Note
This page's custom roles are for your app's own end users signing up through your project's own auth. They have nothing to do with staff access to this console, which is managed entirely from Team.