Admin · Setup
Import workbench
Paste JSON, see exactly what it will do, then apply through an audited database function. Applies run as you, so sign in first.
You are signed out
Previews still work, but every apply will be refused. Go to login.
EnvironmentReadyRoot env loaded
Remote writesTest windowGuarded CLIs
Bootstrap payloadValid1 company, 48 periods
Schema apply50 workbenchespnpm v2:migration-status
Foundation
Owner bootstrap
Bootstrap JSON
Valid55 lines
Preview
Dry run only- Owner
- sammancreative@gmail.com
- Companies
- 1
- Currencies
- NPR
- Active FY
- SCC:2083-84
- Periods
- 48
Apply path locked
Future writes will go through
app.bootstrap_owner(jsonb) after the Supabase mutation window is clear. This screen validates the payload today but exposes no remote write action.Plan
What the owner bootstrap does, in order.
1. Validate bootstrapValidate and enrich the JSON payload locally with generated fiscal periods.ready
2. Apply migrationsApply pending schema and RPC migrations with `pnpm v2:apply-migrations` (psql over SUPABASE_DB_URL).ready
3. Create owner auth userCreate or confirm the owner in Supabase Auth with `pnpm v2:create-test-user` before the RPC runs.ready
4. Apply bootstrap RPCRun `pnpm v2:bootstrap-owner -- --execute` so the CLI calls app.bootstrap_owner(jsonb) with the service role.ready
5. Verify CEO loginSign in as the CEO through /login and confirm profile, membership, company and fiscal period access on /app.ready