PostTrack

Post-production pipeline tracker: projects, deliverables, ingest, studio bookings, and resourcing for a production team.

Structure

• PostProTrackerV4.jsx — the app's source of truth. A single-file React app (no build tooling checked in yet); components, constants, and the top-level App all live in this one file.
• seed_team_members.sql — one-time seed script for the team_members table (run once in the Supabase SQL Editor if that table is empty).
• index.html — a previously-built, self-contained static bundle (React/Recharts/Supabase-JS inlined, no external requests) generated from PostProTrackerV4.jsx. Not auto-generated by anything in this repo yet — treat it as a snapshot, not a build artifact you can trust to be current.
• supabase/functions/ — Edge Functions that need the service-role key (never sent to the browser), deployed separately from the rest of this repo. See below.

Backend

The app is wired to Supabase for auth and persistence (projects and team_members tables so far; other collections still use browser-local storage pending their own migration). See the Supabase project referenced in PostProTrackerV4.jsx's SUPABASE_URL/SUPABASE_ANON_KEY constants.

Two-factor authentication (TOTP) is required on every account, via Supabase's built-in MFA — no extra table or setup needed for that part. One admin action (resetting a locked-out user's 2FA) needs privileged access the browser can't safely hold, so it's implemented as an Edge Function instead:

• supabase/functions/admin-reset-mfa/ — clears a target user's MFA factors; called from Admin → Team's "Reset 2FA" button. Deploy once via supabase functions deploy admin-reset-mfa (or paste index.ts's contents into Dashboard → Edge Functions → New Function, named exactly admin-reset-mfa). Uses SUPABASE_URL/SUPABASE_SERVICE_ROLE_KEY, both already provided automatically to every Edge Function — no secrets to configure. Until this is deployed, that button will fail; an admin can still clear someone's factors directly in Dashboard → Authentication → Users → (user) → Multi-Factor in the meantime.

Status

No build pipeline or CI yet — index.html is hand-assembled (react.js + react-dom.js + prop-types.js + recharts.js + supabase.js + the transpiled JSX, all inlined) rather than produced by a real bundler. Moving to a proper package.json + Vite build, deployed via GitHub Actions to Vercel/Netlify, is the natural next step once the current Supabase integration is confirmed working end-to-end.