· Operators

Admin console

Operator documentation: admin roles, capabilities, platform settings, and the plan catalog.

The admin console at /admin is for operators of a self-hosted TELVRIX deployment. It is separate from workspace administration: workspace owners manage their team, operators manage the platform.

Access

Admin access requires a database-stored admin role. Each admin role carries a set of capabilities, and every admin API route verifies the required capability before acting — there is no all-or-nothing super flag in the request path.

What the console covers

• —Overview — platform-wide counts and health at a glance.
• —Users, workspaces, and mailboxes — search, inspect, and manage tenants. Credential fields are excluded by design.
• —Queue monitoring — live BullMQ counts (waiting, active, delayed, failed, completed) per queue, with per-queue drill-down and job lineage.
• —Worker status — background worker heartbeats with last-seen timestamps.
• —Providers — connection health across mailbox providers.
• —Plans — the plan catalog that drives pricing, limits, and entitlements product-wide.
• —Flags and locks — feature flags for rollout control and operational locks for emergency stops.
• —Platform settings — runtime configuration, platform secrets, transactional email, and status-page notices.
• —Billing — Stripe configuration and billing event history.
• —Audit — administrative action history.

Platform configuration

Runtime behavior is configured from Platform Settings: transactional email (for invite and password-reset delivery), Stripe keys and the webhook secret for billing, the status-page notice, and operational toggles. Secrets are write-only — they can be set and rotated but not read back.

Health endpoints

The public /status page and the /api/health endpoint report live infrastructure state: database configuration, worker heartbeat, and queue health. No synthetic uptime numbers are shown anywhere.