Admin Tour

← Overview AI: Foundation vs. Open-Weight →

This is a guided tour of what an admin can actually do, not a route list — for the operational runbooks (security posture, credential rotation, the Spark Queue build log), see the links at the bottom of each card.

Season Setup & Settings

Before a tournament starts, an admin loads that year's 68-team field and every roster from ESPN, sets the active tournament year, and configures pool-level rules.

  • Import teams and rosters directly from ESPN (search-and-match, not manual entry)
  • Set the active year, round count, and payout threshold
  • Lock or schedule the lock of new entries
  • Download a full JSON backup of users/entries/picks, or restore from one
User & Entry Management

Day-to-day account operations that a player can't do for themselves.

  • View and manage registered users; delete an account or entry if needed
  • Update a user's contact info on their behalf
  • Mark an entry paid, for pools that track a buy-in
Live Data Operations

The scoring engine runs itself once the tournament starts (see How It's Built §6), but an admin has manual controls for when ESPN data needs a nudge or a fix.

  • Force a scoring run instead of waiting for the next automatic check
  • Import season games, betting odds, and tournament scores from ESPN on demand
  • Clean up play-in-round results before the main bracket locks
  • Watch each of these run live via HTMX-polled progress logs
Historical Testing

A dedicated area (separate from live season setup) for testing the scoring logic against a tournament that already happened — see Player Experience §7.

  • Point the active year at a past tournament and re-run the real import-and-score pipeline against it
  • Configure per-year historical dates and rounds
  • Reset historical scores or clear historical data independently of live data
Daily Update — the Three-Generator Eval

The one place the app's two AI approaches are compared directly, side by side, on the same day's data — see AI: Foundation vs. Open-Weight for the full story on what each button actually does and how they've measured.

Generate with Claude Spark — direct call Spark — via queue
Operational Runbooks (not duplicated here)

The admin area also has dedicated ops documentation, kept separate from this player-facing tour on purpose so it can go into operational detail this page shouldn't: an administrator guide (setting a tournament up, day-to-day error handling, historical data → the analytics warehouse), a security posture review, a credential-rotation runbook, and the day-by-day Spark Queue v2 build log. Those pages are linked from inside the admin dashboard for anyone with admin access.