frameworksaas-admin-console · v11099:cursor2026-08-04served from databaseAll documents

SaaS administrator console — standard checklist

SaaS administrator console — standard checklist

Reusable product checklist for any JBNX app that needs a platform-admin console (gated by a platform-admin flag, thin client over server-checked RPCs). Apply to new products as the default admin surface; trim only with an explicit reason.

Live page for this document: /framework/saas-admin-console.

Purpose

Give a platform admin a single place to manage users, households/tenants, billing, support, and ops health — without database access and without exposing service-role keys to the browser.

Access model (always)

  1. Gate the page on a server-checked platform-admin flag (e.g. profiles.is_platform_admin).
  2. Every admin RPC re-checks that flag; the UI is never the security boundary.
  3. Append-only audit log for every privileged action (actor, target, before/after).
  4. Last-admin cannot demote themselves.

The 15 capabilities

Core account management

  1. User / tenant directory — searchable, sortable table: email, display name, created, last sign-in, tenant/household, plan (free / paid / comped), status (active / blocked / admin). Home screen everything else hangs off.
  2. Upgrade / downgrade / extend — grant paid plan, reverse it, change plan code, set or extend period end. Distinguish "comped forever" from "comped until date."
  3. Block / unblock — hard stop sign-in and RPCs; store reason + actor. Distinct from downgrade.
  4. Make / revoke platform admin — promote trusted operators; guard that the last admin cannot be demoted.
  5. Tenant / household inspector — members + roles, resource counts, subscription row, linked support tickets; read-only browse of their data for diagnosis.

Support & safety

  1. Impersonation / support login — short-lived, audited "view as user" session; log who/when; writes off by default.
  2. Billing reconciliation — surface mismatches between payment provider and app entitlements; force-sync and clear orphaned customer IDs.
  3. Support inbox — tickets with status, priority, assignment; link to user/tenant; internal notes; reply that emails the requester.
  4. Audit log of admin actions — append-only trail of upgrades, blocks, admin grants, impersonations, ticket replies, flag changes, CMS publishes, CSV imports.

Ops & growth

  1. Ops health strip — glanceable top bar: deploy SHA / host status, schema/migration drift vs repo, webhook delivery failures, recent 404 spikes, error rate.
  2. Analytics dashboards — signups, activation, retention, plan mix, support volume; privacy-respecting aggregates only (no PII in charts by default).
  3. Email / messaging campaigns — compose and send transactional or broadcast messages to filtered cohorts (plan, status, last active); require preview + confirm; log every send.
  4. Feature flags — per-tenant and global toggles for risky or unfinished features; audit every flip; default-safe when flag missing.
  5. Content CMS — edit in-app copy, legal stubs, help articles, and announcement banners without a deploy; versioned publishes with rollback.
  6. Bulk CSV import / export — export the directory and billing tables; import comps, blocks, and flag flips from CSV with dry-run + row-level errors before apply.

Suggested build order

v1 (minimum useful): 1 → 2 → 3 → 4 → 9 (audit from day one). v1.5 (supportable): 5 → 6 → 8 → 10. v2 (operations): 7 → 11 → 13. v3 (growth / content): 12 → 14 → 15.

Out of scope for this checklist

Adoption notes for agents