Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.time2.bike/llms.txt

Use this file to discover all available pages before exploring further.

Permissions are checked at three layers: account, organization, and timing session.

​
Account

A signed-in user is just a rider by default — they can register, manage their own registrations, sign waivers, and edit their profile.

​
Organization roles

Set on the Settings → Team page of each org. A user can be in many orgs, with a different role per org.
RoleWhat it’s for
ViewerRead-only access to org data.
TimerManage bib assignments and race timing.
FinanceManage billing and payouts.
ManagerCreate and edit events, races, pricing, and merch.
AdminFull access including team management and destructive actions.
The user who creates an org becomes its first Admin. You can’t remove the last admin — promote someone else first.

​
Timing session roles

For race day, scoped tokens can grant a narrower set of permissions on a single session (see Roles):
RoleCapabilities
viewRead-only operator screen.
timerRecord finishes, plates, lane starts/finishes, self-clear.
marshalAbove + manual times, status changes, notes, deletes.
adminAbove + finalize, publish, issue new tokens.
refundReserved.
Token roles do not stack with org roles. A volunteer with a timer token cannot edit registrations elsewhere in the org.

​
Participant access

Riders can grant other people limited access to their registrations:
  • viewer — see registration details only.
  • editor — change race / category / answers.
  • manager — full control including transfers.
Set this on a rider’s account → Participants page or from a participant card in the registration flow.

​
Rider data access

Riders control how their data is shared via Account → Privacy (data export and account deletion). Public pages — like results and start lists — show a rider’s name as part of an event they registered for. See Privacy.