Roster and invites
Add players to your roster, then press Make logins. Each player gets a username (their first name plus a team suffix, never a full name) and a one-time starter code, printed on a card you hand out; on first sign-in the player picks a password you never see. No player email is collected. Lost the card? New code on the player's row issues a fresh one, the reset is recorded, and the player is told at their next sign-in. A player can instead claim an account through an email invite link, if your program prefers that. Either way a player's account is completely separate from a coach's — it isn't a coach account with fewer buttons.
What players see
Nothing, until you publish it. A play is invisible to players until you mark it installed. Players never see your call sheets, practice scripts, scouting reports, self-scout, or each other's quiz results.
The engagement dashboard is coaches only. A player who opens a coach page is sent back to their own app — and underneath that, the database itself refuses them the data.
Deliveries
Push a play, practice script, or scouting report to your players or staff as an alert, with an optional note. Players can view, acknowledge, and react — there is no reply, and no messaging anywhere in this app, by design.
Quizzes
Two kinds. The practice quiz generates itself from your installed, tagged plays and needs no setup. Coach-authored quizzes are ones you write: your question, your answers, one marked correct, optionally with a play's diagram alongside. Write them under Team → Quizzes, publish when ready, and the Results page shows the answer key with a per-question miss rate plus what each player picked.
Answers never reach the player's browser. Quizzes are graded on the server, so the key can't be read out of the page.