Admin Log In
Mint a session
Card and deck content stays in Supabase. This form only sets up the table for one engagement.
These three are locked to the session. Dealers never see or change them.
Set this to whenever the engagement actually ends, including the debrief. There is no separate start time; the code is live from the moment you mint it.
Active sessions
Add a deck
Creates a new version. Use this once per deck, then add its cards below. For loading many cards at once, the SQL snippet in the admin guide is faster.
Add a card
Adds one card to an existing deck. The deck and card type stay set after each save, and the card number advances, so you can add a whole pile in a row.
Position within this pile. Suggested automatically from the deck and type above; change it if you want to leave a gap or reuse a retired number.
Shown on the card as a round badge. Leave blank to hide the badge.
Difficulty is optional everywhere by design; a missing or mistyped value never blocks the deck. Postgres will reject the save if a card is missing the text a player actually needs to see (for example, a situation card needs both a title and a body).
Curated hands
Scripted hands belong to the deck, not to any one session. Turning on "Curated hands" when minting just deals from whatever hands already exist here for that deck, in set number order.
Add or edit a hand
Hands are dealt lowest to highest. Gaps between numbers are fine.
One or more conversation cards dealt as this hand's angles.