*Team roster (admin) lists people who appear in logistics crew pickers* and related tools.
| Task | Why it matters | |
|---|---|---|
| Add new crew for the season | They can be assigned on race weekends | |
| Deactivate leavers | Stops accidental assignment to old events | |
| Keep roles accurate | Briefing and logistics filters use roster data | |
Team admins maintain their own roster. Super-admins can view across teams.
*Staff resources shows who is on which car* in the workshop or paddock — a live board for coordinators.
Typical use:
- Shift lead marks crew *on car / off car* - Race engineer sees coverage before session - Team manager spots gaps without radio round-robins
Data is operational, not a time-and-attendance legal record unless your programme defines it that way in policy.
Where *car tablets are deployed, crew authenticate and scan car QR* codes to open the right job context. Tablets should stay on the team network or VPN policy your programme defines.
A fixed *kiosk or laptop can scan a member’s membership QR to open their weekend briefing. See Race weekends and logistics* for how briefing packs are built.