The operations console is the control room for race programmes. Open it from *Admin login* after your credentials are accepted.
| Menu | Purpose | |
|---|---|---|
| *Dashboard* | Programme snapshot, signup counts, shortcuts to public demos | |
| *Card studio* | Global default card theme | |
| *Memberships* | All membership applications | |
| *Membership billing* | Billing settings and plans (where enabled) | |
| *Showroom* | Manage cars listed on the public showroom | |
| *Store requests* | Incoming parts reservations | |
| *Parts catalog* | Programme-wide or team catalogue maintenance | |
| *Teams* | Register teams, hostnames, programme flags | |
| *Team roster* | Staff linked to logistics and crew pickers | |
| *Staff resources* | Live workshop / paddock presence | |
| *Race projects* | Weekend logistics (events, crew, hotels, sessions) | |
| *Tracks catalogue* | Circuit layouts used in logistics | |
| *Scrutineering* | Event passes and scrutineer handoff | |
| *Car management* | Clients, cars, documents, race bookings | |
| *Site editor* | Programme marketing pages (super-admin scope) | |
Team users see a *tile dashboard* instead of the full super-admin list:
- *Race weekends* — logistics and briefing packs - *Cars & customers* — car management - *Parts catalog / Price requests* — store - *Membership cards* — card studio for your team only - *Team roster* — who appears in crew lists - *Staff resources* — who is on which car - *Website editor* — your team’s public microsite pages and colours
Restricted logins see only the tiles your administrator enabled.
Use the *language* control in the admin top bar. All labels follow the same locale files as the public site.
- Use *one browser profile* per role on shared PCs (avoid mixing super-admin and team tabs). - After editing *logistics or cars, confirm crew-facing briefing* links still work before the event. - Export or screenshot critical weekend packs if you need an offline backup — the platform is the source of truth, but circuits lose signal.