Start here

Before operating the Hub, confirm you are using the intended environment and your own account has the needed role. Do not use another person’s account or an impersonation view to make changes.

Operating model

The application is a single-event React SPA with Supabase authentication, Postgres/RLS, Storage, Realtime, and Edge Functions. Admin, sponsor, speaker, and attendee journeys are distinct. Public pages intentionally remain public; private resources rely on RLS and server-side authorization, not a hidden URL.

Event-day handoff

1. Name the on-duty organizer, technical owner, and communications owner.
2. Open the command center and review active incidents/tasks.
3. Confirm access to admin, check-in, CMS, and support channels without exposing credentials.
4. Use the incident runbook for failures that affect participants, payments, privacy, or event operations.

Help boundary

Link attendees, sponsors, and speakers to the relevant in-app guidance. This handbook can describe internal procedures, but it must never reveal private rosters, invitation contacts, moderation history, secret configuration, or a recovery bypass.