Livingston Township

Operations guide

How CSE works

A walkthrough for the people who run the show, not the people who built it. Pick a persona below to see what they sign in as, where they go, and what they actually do on a typical day. Same show, same neighbors, same vibe — just phones in place of clipboards.

One sign-in, all roles

There is exactly one place to sign in. Every role — car owner, attendee, gate volunteer, judge, DJ, vendor, organizer — uses the same form with their issued email + password. The system reads the user's role membership and routes them to the right starting page automatically.

Universal sign-in URLOpen
  • Each persona below shows a ?next=/path deep-link so the user lands in the right place after auth.
  • The livingston4th subdomain isn't a separate login — it's how the platform identifies which tenant the user is signing in to.
  • Today this admin app is un-gated in dev — when auth lands here it will share the same eventide_session cookie, not a separate login.

Pick a persona

Start here. Each persona shows their own login, their walkthrough, and quick links to where they live in the system.

Clear selection

Platform admin

Operations console for CSE platform staff (not Livingston). Visually different from tenant admin — amber accent everywhere, sticky banner at the top reading "PLATFORM ADMIN — actions here affect every tenant." NORAD-meets-Stripe-internal: dense, instrumented, intentionally a little intimidating.

What this persona can do

  • Tenants: dense data grid — name, plan, status, active events, MRR, owner email, last admin sign-in. Bulk-suspend, bulk-announce.
  • Impersonate as TENANT_ADMIN (red, double-confirm, audited).
  • Health: live SSE charts — API p95, error rate, queue depths (sms-send, refund-process, media-transcode), Redis memory, Postgres pool.
  • Releases: deploy history, rollback (requires typed commit-SHA confirmation).
  • Feature flags: per-tenant matrix. Bulk-flip via column header.
  • Cross-tenant audit feed with severity filter (info / notice / elevated / security).
  • Every destructive action is a 2-second hold-to-confirm (long press with a progress ring).

Walkthrough

5 steps

A platform-staff afternoon

  1. Open Platform admin

    Sign in with super@eventide.app, route to /platform. The amber sticky banner reads "PLATFORM ADMIN — actions here affect every tenant. Audit logging is in elevated mode." That banner means you're in god-mode.

  2. Onboard a new township

    Tenants → "New tenant." Form: name, slug, owner email, plan. On save, sends an onboarding email to the owner with a one-time sign-in link. They land in tenant-admin onboarding.

  3. Investigate a flagged tenant

    Tenants → click row → drawer opens (640px wide). Recent activity, audit entries, billing health, internal "platform notes" only platform staff can see. "Impersonate as TENANT_ADMIN" button at the bottom — red, double-confirm, fully audited.

  4. Roll back a bad deploy

    Releases → most recent row. Rollback button, type the commit SHA to confirm. No accidental rollbacks.

  5. Flip a feature flag

    Feature flags → matrix view. Toggle FEATURE_PAYMENTS_STRIPE for Livingston when they're ready to take cards.