A Stintsmith team is a small permission scope, not a community. Everyone you invite gets access to your team’s laps, races, stint plans, and timing — and nothing outside it. The way you grow the team is the same regardless of plan: open an invite, share the link, and assign a role when they join. Roles are flat; there is no hierarchy of approval and no sub-team. The whole point is that a captain can do this in two minutes between sessions.
Share an invite link
Open Settings → Invites on the desktop. The page offers two ways to bring a driver in. The first is a tokenised join link — pick the role you want the new member to land in, optionally cap the maximum uses and the expiry, and the system mints a URL of the form https://stintsmith.com/join/<token>. Paste that wherever you already organise the team (Discord, WhatsApp, Slack). Anyone who clicks the link is bounced through sign-in, lands on a confirmation screen with the team name and the role you set, and joins on click.
The second is an email invite — type one or many addresses, set the role, and the portal sends a one-time link to each address. Email invites are the right choice when you want the audit trail (the request goes out under your name, the acceptance is recorded against the email), and when the people you are inviting are not already in the team Discord. For a quick roster fill, the link is faster.
Each token can be revoked at any time from the same page. Revoke a link and any pending clicks on it fail with a clean message rather than a silent skip; the people who joined before the revoke keep their seats.
How roles work
Six roles, each with a clear contract:
- Admin. Full read and write on every team surface. Can invite, remove, and re-role members. Can edit team billing. Use this sparingly — at most a couple of people per team.
- Captain. Race ops without billing — can create races, build stint plans, run a race weekend, and invite drivers. The default role for someone you trust to organise a weekend.
- Engineer. Read-heavy on telemetry, can write annotations and setup notes, can stage stint plans for the captain to lock. The right role for a strategist who never drives.
- Coach. Read access to laps and telemetry across the team, can post coaching notes on individual laps. Cannot create races or edit stint plans. Use this for a guest coach helping a single driver.
- Driver. The default role. Full access to their own data, read access to the team, can RSVP to races and run stints assigned to them. Most members live here.
- Reserve. Same as Driver but does not count against the seat cap and is not eligible for stint assignment by default. Keep an off-roster driver paired with the team without burning a seat.
Roles change live from Settings → Members. The dropdown next to each member updates immediately; the affected user’s next page load reflects the new scope. There is no “you are about to lose access” warning because the system will never let you remove the last admin from a team — that path returns a clean error rather than locking the team out.
Transfer a driver between teams
Driver transfers are first-class because endurance teams trade rosters. Open Transfers from the side nav. The page lists open listings — drivers looking for a new team, and teams looking for a driver. To move someone from your team to another, the driver themselves creates a listing (under the same page, with Make me available), the receiving team makes an offer, you accept it, and the transfer completes on a clean cut-over.
Crucially, the driver’s laps, telemetry, and annotations stay with them, not with the team they leave. What changes hands is the team membership and any future data they record. Historical results in your team’s race records keep their names — the transfer does not rewrite history. If you need to move a single driver and don’t want to use the public listing flow, an admin on both teams can complete the handover directly from the same page; the audit log records who initiated the move.