Roles and permissions
Everything about people is managed on the "Team" page. What a person can do is set there too, per person: an access preset as the starting point, plus optional overrides.
Roles
| Role | Badge | What they can do |
|---|---|---|
| Owner | Owner | The account that owns the organization. Can never be demoted or removed. |
| Admin | Admin | Full control within the org: manages members, roles, passwords, access and master data. Holds every permission, always. |
| Member | Member | The default. What they can do is set by their access preset and overrides. New members start on Standard member. |
| Project admin | N projects | A member with full control of specific projects, granted per project from Team → Project admins or at invite time. Holds every permission inside those projects. |
Safety rails, enforced server-side: the owner can't be demoted or removed, you can't demote or remove yourself, and an org can never be left without at least one admin.
Access presets
Every member has one access preset, a named bundle of permissions that is their starting point. To change it, open the member's row on Team and click "Access". The preset saves as soon as you pick it.
- Standard member — Everything a member could do before presets existed, except running the job board, Operations and approving costs.
- Read-only — Sees everything, including finances; changes nothing.
- Mechanic — Parts, measurements, rebuilds, laps and setups. Works the jobs assigned to them and runs the board of any car they lead. Can't change lifing limits.
- Chief mechanic — Everything a mechanic has, plus the whole job board: create, assign, acknowledge and delete any job.
- Race engineer — Sessions, laps, setups, measurements and notes.
- Operations — Crew, people, travel and Trip plans. No parts or lifing data; can't create events.
- Team manager — Everything except seeing, managing and approving finances. Submits their own costs and receipts for approval ("My expenses").
- Finance — Sees and manages the ledger, budgets and receipts; approves expenses.
- Custom — Nothing by default: only the permissions you switch on.
Existing members were moved to Standard member when presets arrived. It keeps exactly what they could do before, so nobody lost access on the day it shipped. Anyone who had Manage events also received Run Operations, so their crew and travel work carried on.
:::warning Standard member includes finances Standard member includes See finances and Manage finances. That means every standard member can see the whole ledger and edit any line. If that isn't what you want, move the person to another preset, or deny those two permissions (see Team, roles and permissions). :::
Overrides: Allow and Deny
On top of the preset, an admin can set any of the 20 permissions to Allow or Deny for one person. Each row on the Access screen shows where its current state comes from: the preset, an override, or a project Allow.
- Org-wide (the default scope) applies in every project. Here each permission offers Preset (follow the preset, with a tick when the preset includes it), Allow or Deny.
- A single project (pick it from the scope selector) offers Org setting (follow the org-wide rule) or Allow. A project Allow works only for areas that belong to a project (see below). Where it works, it lets the person do that inside the project even where the org-wide setting denies it. A project can grant a permission, but it can't block one.
- Deny is always org-wide.
- Clear scope removes every override in the scope you are viewing. The preset still applies.
Changes take effect as soon as they are saved. The person's screen picks them up when they return to the app.
:::info Org admins hold everything An org admin holds every permission in every project, so their Access screen has nothing to set. To give an admin a preset or individual permissions, change them to Member on the Team page first. :::
The 20 permissions
The Access screen groups the 20 permissions into five groups. Each permission is listed with the label and description the screen shows.
Parts & lifing
Parts, mileage and life limits, and the measurements and rebuilds that feed them.
| Permission | What it lets the person do |
|---|---|
| See parts & lifing | See parts, mileage, lifing alerts, rebuilds, measurements and which parts ran in each session. |
| Manage parts | Add, move and edit parts, assemblies and tyres. |
| Log measurements | Add measurement readings on parts. |
| Part notes & photos | Add notes, photos and inspection findings on parts and chassis. |
| Mark rebuilds | Log rebuilds, which reset a part's wear cycle. |
| Edit lifing limits | Change life limits, warning thresholds, a part's starting km/hours/expiry and manual mileage corrections. |
Trackside
Day-to-day logging at the track.
| Permission | What it lets the person do |
|---|---|
| Manage sessions | Create, edit and delete sessions, session templates, goals and reference times. |
| Log laps & runs | Record laps, runs, weather, tyre use and incidents per session. |
| Edit setups | Choose which parts run on which car per session, and the car setup sheets. |
Events & operations
The race calendar, crew, people and travel.
| Permission | What it lets the person do |
|---|---|
| Create & edit events | Create, edit and delete events, seasons and championships. |
| Run Operations | Crew, people, travel and Trip plans (bookings, rooms, documents, share links). |
Team structure
Cars, projects, the mechanic job board and general team data.
| Permission | What it lets the person do |
|---|---|
| Manage cars | Create, edit and delete cars and their documents. |
| Manage projects | Create, edit and delete projects and their weight config. |
| Manage mechanic jobs | Create, edit, assign and close jobs on the Mechanics page. |
| Work on mechanic jobs | Move and annotate the jobs assigned to you and claim unassigned ones. On a car you lead (crew role flagged “leads a car”, or the lead set in Settings → Mechanics) you also create, assign, edit and delete jobs; acknowledging stays with “Manage mechanic jobs”. |
| Edit everything else | Drivers, debriefs, reports, snags, event notes, strategies, team timer and other team data. |
Finance
The ledger, budgets, receipts and expense approvals.
| Permission | What it lets the person do |
|---|---|
| See finances | See the whole ledger, totals, budgets and every receipt. |
| Manage finances | Add, edit and delete any ledger line, receipt or budget. |
| Submit expenses | Add own costs and receipts for approval; sees only their own lines. |
| Approve expenses | Approve or reject submitted costs. |
What a permission does
Each permission is enforced by the database for the data it covers, so the rule holds even if someone works around the screen. The screens hide the controls a person can't use, so you won't see buttons that fail.
A few things to know:
- Some actions need two permissions. Propose part swap needs Manage parts and See parts & lifing. Log measurement on a job needs Log measurements and See parts & lifing.
- Without See parts & lifing, screens that need the data show "You don't have access to parts and lifing data" instead. On an event, that is the Mileage tab.
- Events, sessions and laps can be read by every member. The permissions above control who changes them.
- Approving a part swap needs Manage parts, on top of being the designated approver (see Part swaps and measurements).
- A project Allow only works for some areas. Data that carries its own project responds to it: parts and assemblies, cars, projects, seasons, session templates, drivers, crew (personnel), mechanic jobs, and a project's own life limits and weight settings. Everything else, including laps, setups, measurements, rebuilds, part notes and finances, follows the org-wide setting only. Set those permissions org-wide.
Adding people
Two paths from Team → "Add a team member":
- "Create account" — email + role + generated password; works instantly, no email server needed. Ideal at the circuit.
- "Invite link" — a link valid 14 days; the invitee signs in (or signs up) with the invited email and accepts. If the emails don't match, the accept button is disabled with a clear message. Pending invites can be copied or revoked from the Team page.
Either way, the new person starts on Standard member. Change it under "Access" if they need more or less.
Password resets are also admin-driven: Team → "Password" sets a new one you hand over ("Password updated. Share it with …").
Related
- Team, roles and permissions — step-by-step: presets, overrides and common setups
Was this page helpful?