Each module already documents its permissions in its own "Who can do what" section — this
page brings them all together in one place, so you don't have to hunt them down one by
one.
Roles covered
The tables below focus on the logistics coordinator / logistics assistant distinction,
the most fine-grained and most consulted one. For sector members and the organization
administrator, see Sector Space and Admin
Space respectively.
An account can hold several roles at once: they stack (the transport lead who also
delivers equipment, for example, holds both "Transport lead" and
"Logistics assistant").
System roles — present in every organization, cannot be deleted:
Role
Who
Organization administrator
manages everything in their organization, has access to all spaces
Logistics coordinator
drives logistics end to end
Logistics assistant
prepares and executes, without the structural decisions
Committee roles — created automatically with your organization, for the usual
functions of an organizing committee:
Role
What it covers
Chair
overview of all modules, read-only, plus exports
Treasurer
invoices (from verification to payment) and budget envelopes
Race lead
race schedule, sectors, locations, incidents
Bib lead
cross-sector visibility; the real work happens in their sector
vehicle fleet, planning, forced returns at the depot kiosk
Communications lead
document templates, letterheads, day-of display
These nine roles are a starting point, not a fixed framework: the organization
administrator adjusts their permissions in the matrix, deletes them if they don't match
anything at your organization, and creates others — see Admin Space → Global
Roles.
Functions tied to a location are sectors
Bib numbers, refreshment stand, aid stations, speaker… are first managed as sectors
(with a sector lead), not as global roles. A global role is only useful for what goes
beyond a single sector. See Sector roles.
Creation is reserved for members with the "can submit requests" capability; validation
is reserved for the logistics coordinator. Accepting or rejecting an
amendment on an already validated request follows the
same rule.
The logistics coordinator always has access to the full set of actions. The logistics
assistant can view and move day-to-day work forward (receiving, distributing,
planning), but structural or irreversible actions — validating a request, cancelling a
finalization (except for distributions), closing a return, managing the fleet or the
budget — remain reserved for the coordinator.
"Reserved for the coordinator" is a default setting
Unless stated otherwise, these splits are the ones shipped when the organization is
created. The organization administrator can change them in the permissions matrix
(Admin → Roles) — for example granting "Set the budget" to the treasurer, or "Decide on
an amendment" to the assistant.
Two limits don't move from the matrix, no matter which box is checked:
Actions on equipment (planning and carrying out distributions, receiving,
viewing supplier contact details) remain reserved for logistics roles — this is
the "logistics is the only actor that touches equipment" rule. For another role to
get access, add them the Logistics assistant role on top of their own.
The Organization administrator role cannot be removed from the last
remaining administrator.