Settings, catalogues and branding
Settings is organised in sections (left rail): General, Inventory, Tyres, Events, Mechanics, Workshop, Team & people, Activity log. The highlights, by what teams actually look for:
Your component catalogue
Settings → Inventory → "Your components" is your org's private catalogue of part categories. Per category: name (unique within your org), short code, colour, EOL limits (km — derated by each part's target use — plus optional hours and events), warn/critical % thresholds, a position set (corners FL/FR/RL/RR, sides, axles or custom labels), max per car and per assembly, a parent category (for sub-components like Engine → Turbo), and a measurements schema (the fields mechanics log, with motorsport units). A category can't be deleted while parts use it.
New orgs start from ICRX's template catalogue and diverge freely — your copy is yours.
Other catalogues
- "Part locations" (Inventory) — where spares live (containers, shelves). Org admins edit; the labels feed every location picker.
- "Tyre compounds" (Tyres) — rename, recolour or deactivate compounds; every compound chip in the app follows.
- Tracks (Events) — the circuit list itself is global (curated by ICRX; ask if one's missing), but "Track length — your org" lets org admins override a lap length just for your data.
- "Session templates" and "Box Timer templates" (Events) — reusable session sets ("FP1+FP2+Q+R1+R2") and Box Timer day plans.
Branding and identity
- "Team logo" (General, org admins) — upload square logos (light/dark) for the sidebar and wide wordmarks for the sign-in screen. This is the white-label surface: with a vanity subdomain (
yourteam.icrxms.com, provisioned by ICRX), your people sign in under your brand. - "Team profile" (General, org admins) — short name, FIA code and country; stamped into FIA export file names and headers.
- "Appearance" — per-user theme (Light / Dark / OLED) and finish, plus the per-team accent colour with a live WCAG-contrast check so your brand colour never makes buttons unreadable.
Data out
"Download backup (.json)" (General) exports the whole org — cars, parts, mileage, events, tyres, assemblies, drivers, settings — into one file, client-side. The Inventory page exports CSV; parts and cars export PDFs (logbook, dossier, spec sheet).
Activity log
Settings → Activity log is the org's audit trail: who changed what, when — filterable by person and event type. Every destructive action in ICRX notes that "the audit log keeps the history"; this is where it lives.
Related
Was this page helpful?