Team, roles and permissions
The Team page is the home for all people. Four tabs: Members (app accounts), Crew (everyone in the operation, login or not), Project admins, and Invitations.
Adding members
Access is invitation-only. "Invite" (admins) offers two modes:
- "Create account" — you set the email and a generated password, hand both over, done. No email server involved. Ideal at the workshop: create the account, the mechanic signs in on the spot.
- "Invite link" — generates a URL valid 14 days; the invitee signs in with the invited email and accepts. Pending links are listed under Invitations with "Copy link" and revoke.
Both modes pick a role — Member or Admin — and optional per-project admin grants.
Lost password? There is no self-service reset: any org admin uses "Password" on the member's row to set a new one and share it.
Roles in one minute
- Member — read-write on project data; specific abilities via permissions below.
- Admin — full control of the org (members, branding, master data); implicitly holds every permission.
- Project admin — full control inside one project (granted on the Project admins tab or at invite time).
- Platform / Owner — ICRX-level roles for global catalogues and org management; regular teams never need them.
Admins can't demote themselves, and the owner can't be demoted — no lockouts.
Granular permissions
"Permissions" on a member's row opens the grants editor. Pick a scope — Org-wide or one project — then toggle keys, organised in three groups:
- Trackside data entry: Log measurements · Write part notes · Mark rebuilds · Log session laps · Edit session setups.
- Inventory & jobs: Manage parts · Manage mechanic jobs.
- Structure & planning: Manage sessions · Manage events · Manage cars · Manage projects.
Two of those keys gate real product areas today: "Manage mechanic jobs" (without it, the job board is read-only) and "Manage events" (event crew, travel and crew templates). The rest are recorded and shown in the summary, but don't restrict what a member can do yet — more areas move under granular control over time. Day-to-day logging never needs a grant.
Quick grant presets stamp common bundles: "Mechanic", "Race engineer", "Team manager". The "…can" summary at the bottom lists every grant across scopes. Org-wide grants apply on top of project ones.
Crew and drivers
- Crew (Team → Crew) — people with job roles (Race Engineer, No.1 Mechanic, Tyre Technician…) used for event staffing. Job roles organise people; they don't grant app permissions. "Import N drivers" pulls existing drivers in as crew.
- Drivers (Settings → Team & people) — name, initials, race number (unique per org) and FIA licence. Needed for FIA exports and per-event seat assignments.
Related
Was this page helpful?