Skip to main content

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. A new member starts on the Standard member preset. You can change it under "Access" once they exist (see below).

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 — what they can do is set by their access preset and overrides.
  • Admin — full control of the org (members, access, branding, master data); 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.

Access: presets and overrides​

Each member has one access preset, shown as a badge on their row in Members. A +N custom badge means they also have overrides. The presets and what each one includes are listed in the reference.

To change someone's access, click "Access" on their row (admins only). The screen has three parts:

  1. Access preset — pick a card. It saves straight away.
  2. Scope — Org-wide, or one project.
  3. The 20 permissions — in five groups. Each row says where its current state comes from ("allowed by the preset", "blocked by an override", "not in the preset") and has a switch: Preset, Allow or Deny (org-wide). Inside a project the switch is Org setting or Allow.

The "…can" summary at the bottom lists, in plain words, what the person can do in the scope you are viewing.

A few rules to keep in mind:

  • Deny is always org-wide.
  • A project Allow works only for areas that belong to a project: parts, cars, seasons, crew and similar (the reference lists them). Where it works, it lets the person do that inside the project even if the org-wide setting denies it. A project can grant a permission, but it can't block one.
  • Clear scope removes every override in the scope you are viewing. The preset still applies.
  • Org admins hold every permission, so their Access screen has nothing to set. To give an admin a preset, change them to Member first.

Common setups​

Runs Operations, but no mileage and no event creation​

Set the preset to "Operations".

  • They can run crew, people, travel and Trip plans, and see events, sessions and laps.
  • On screens that need parts and lifing data, such as an event's Mileage tab, they see "You don't have access to parts and lifing data" instead.
  • "Add event" stays hidden, because creating and editing events needs "Create & edit events".
  • The preset includes "Submit expenses", so they also get "My expenses" (see below).

Read-only​

Set the preset to "Read-only". They can see parts, lifing and finances, and change nothing. If they shouldn't see money, add a Deny on "See finances".

Costs seen by two people, receipts from everyone​

  • The two people who should see the money: add an org-wide Allow on "See finances" to the preset they already have. If they also need to manage the ledger, use the "Finance" preset, which adds "Manage finances" and "Approve expenses".
  • Everyone else: a preset that includes "Submit expenses" but not "See finances": "Mechanic", "Chief mechanic", "Race engineer", "Operations" or "Team manager". They see only their own lines and receipts.
  • "Standard member" includes "See finances" and "Manage finances". Move those people to one of the presets above, or deny both.

Org admins always see everything.

An expense approver​

Give them "Approve expenses": an org-wide Allow on their current preset, or the "Finance" preset, which includes it. Without "See finances", an approver sees every line and its receipts, but no totals, budgets or charts. For someone who only approves, "Custom" with that one permission switched on also works.

An approver who also holds "Submit expenses" (say a "Team manager" with an Allow on "Approve expenses") files their own costs from the same page: it has "Scan receipt" and "Add cost", and they can edit or delete their own lines that aren't approved yet. Their own lines always need another approver.

Here is how a cost moves:

  1. Anyone who isn't an org admin adds a cost, or scans a receipt. That includes people with "Manage finances" and the "Finance" preset. The line starts as Pending and isn't in the totals yet. Two kinds of cost skip this step and count straight away: costs an org admin enters, and costs that come from a priced booking in the Trip plan (nobody approves those; the booking is the record).
  2. The approver opens the ledger and clicks Approve or Reject on a line, or on several at once. Where the ledger starts depends on what they see: an approver without "See finances" starts on the lines waiting for a decision (the Pending status filter); someone who also sees finances, such as the "Finance" preset, starts on every line and picks Pending (or the "N pending approval" button) to see what waits. A rejection can carry an optional note, which the submitter sees.
  3. Approved lines count in the books. Rejected lines stay out, with the note beside them.
  4. The submitter can edit a rejected line, an approver who also holds "Submit expenses" included. Saving it sends it back to Pending.

Each decision is recorded with who made it and when. An approver decides other people's lines. In the app, they edit only their own lines, and only with "Submit expenses", or any line with "Manage finances". The database itself is a little wider: an approver without "Submit expenses" can still change a line they submitted while it isn't approved (outside the app, for example through the API). That change sends the line back to Pending, and another approver has to decide it.

Export CSV on the ledger writes each line's status in its approval column as submitted, approved or rejected: submitted is the line the screen shows as Pending.

Nobody approves their own expense — except the boss. An org admin can approve their own costs. Everyone else, including someone on the "Finance" preset, needs a second approver: their own lines show "Needs another approver" instead of the buttons, and if they edit one of their own lines it goes back to Pending. The same holds for any line: when someone other than an org admin changes what a line says (amount, date, supplier, description…), it goes back to Pending, and that person can't approve or reject it — the line shows "You changed this line — another approver has to decide it". Attaching a receipt, tagging a car or marking a line "Not a duplicate" doesn't count as a change. You decide who can approve on the Team page.

A mechanic who logs jobs but can't change life limits​

Set the preset to "Mechanic". It includes "Work on mechanic jobs" (the jobs assigned to them, and the board of a car they lead), the parts, measurement, rebuild, lap and setup permissions, and "See parts & lifing", but not "Edit lifing limits". It also includes "Manage parts", which the part-swap approver needs in order to apply swaps. To run the whole job board, use "Chief mechanic", which adds "Manage mechanic jobs".

My expenses​

Someone with "Submit expenses" but neither "See finances" nor "Approve expenses" opens Financial and sees "My expenses". They can scan a receipt or add a cost, see only their own lines and receipts, and check the status of each one: Pending, Approved or Rejected, with the approver's note on a rejection. There are no totals, no budgets and no other people's lines.

Scanning a receipt, here or on the ledger, opens a review sheet: the app reads the supplier, date, total, VAT and currency, and you check them against the photo before the cost is filed. Every receipt needs you to tick a box that reads "I checked the amount and date it read against the photo" (for example "I checked €108.97, 13 Apr 2026 against the photo"), even when everything was read cleanly. The same box comes back when you edit a cost that has a receipt. Pressing Enter never files a receipt you haven't confirmed: it takes you to the next field that needs a look, then to the box; Space ticks it, and Enter on the ticked box saves. Costs you type in with "Add cost", and Trip-plan costs, don't ask for it. A field read with low confidence, or not read at all, also needs its own "Looks right" (or a value you type in). If you change the amount, currency or date after ticking, the tick clears and you check again.

Once one of their costs is approved, its receipt stays: only someone with "Manage finances" can delete it. A receipt they discard while reviewing it leaves their list, and they can't bring it back themselves; a finance manager can restore it from Financial → Receipts.

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. Adding or editing people here needs "Run Operations". "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.

Was this page helpful?