Platform (Novalien staff)

For Novalien staff only. This section is publicly visible so staff can reference it from anywhere, but operating the customer-facing UI is not your job — customer admins go to /admin/.

What is different here from every other section: you operate across orgs. Your identity lives in platform_users, not users. Your login is /platform/login, a different route from /login. Your JWT carries no org_id claim and alone cannot reach any /api/v1/... org endpoint. To act inside a customer org you mint a scoped impersonation token (D80) — a 30-minute, non-refreshable JWT bound to exactly one target org, logged to both the platform audit log and the target org’s audit log. The customer’s Owner can revoke your access at any moment via the allow_platform_impersonation toggle. Every action you take is audited. Act accordingly.

Scope inclusions: onboarding and 2FA enrollment, scoped impersonation, cross-org search, feature-flag rollout, release-pipeline monitoring, incident response. Out of scope here: any customer-facing UI path (see /admin/, /operator/), engineering-only runbooks (those live in docs/superpowers/plans/ in the repo).

Start with this flow

1. Set up your platform account and 2FA
2. Use scoped impersonation
3. Audit expectations
4. Search across orgs
5. Run a feature-flag rollout
6. Respond to a P1 incident

Common urgent tasks

• Respond to a P1 incident — first 30 minutes.
• Use scoped impersonation — the D80 mental model and token lifecycle.
• Rotate a stuck secret
• Emergency LLM failover
• Revoke platform-admin access
• Archive an unpaid org
• GDPR deletion

If something is broken

• Customer report not reproducible
• Audit log investigation
• Per-customer data export

Reference

• Audit expectations — what gets logged, where, for how long.
• Five-role RBAC — where platform_admin sits in the hierarchy (D78, D80, D86).
• Roles and permissions — endpoint-level matrix.