Verify runtime health before or after operator actions.
./bin/admin-local ops health-summary
Platform health and recent activity
Use the left rail or Cmd/Ctrl+K to move between focused operator pages without leaving the admin shell.
Use the hosted portal for the high-frequency support and QA flows that need audit logs and shared context.
These are the server-local commands that pair best with the hosted portal when you need shell access or automation.
Verify runtime health before or after operator actions.
./bin/admin-local ops health-summary
Inspect a customer’s auth state before running repair mutations.
./bin/admin-local auth show-auth-state user@example.com
Audit push registrations directly from the server-side CLI.
./bin/admin-local notifications list-devices qa-demo@yopmail.com
Check whether this browser already has an operator session, or sign in with the dedicated portal account.
Visible session feedback for sign-in, check-session, sign-out, and MFA state.
Check the current browser session or sign in with password plus TOTP or a recovery code.
Check the current browser session or sign in with password plus TOTP or a recovery code.
Database, worker heartbeat, environment flags, and forecast freshness.
Sign in to load runtime health.
Sign in to load runtime health.
A quick read on recent privileged actions before opening the full audit feed.
Sign in to load recent operator activity.
Sign in to load recent operator activity.
Move directly into the most common support and ops tasks without hunting through the portal.
Keep the portal aligned with the operator docs, CLI, and machine-readable registries.
The canonical docs shell for admin APIs, CLI groups, and admin workflows.
How the hosted portal, operator APIs, and CLI fit together.
Machine-readable command metadata generated from the same backend-owned registry.
Project defaults for docs-first behavior and operator tooling safety.
Search by email or ID, load the backend-owned user profile, and run audited account repair flows without leaving the page.
Create fresh test accounts with auditable presets, or seed a complete demo workspace with a route, plan, trip, and current forecast favorites for docs and operator QA.
Search results capture user context automatically and hydrate downstream route-owner and repair fields.
Repairs are scoped, justified, and written to the operator audit log.
Structured account details on top, raw JSON underneath.
Sign in to search users and run support actions.
Sign in to search users and run support actions.
Move from owner lookup to route inspection, terrain analysis, route-plan review, and trip-safety detail without leaving the portal.
Start from a customer email to list saved routes or route plans.
Inspect one saved route or run support terrain and exposure workflows.
Follow a plan into recent or latest trips, then open the full trip support summary.
Use the structured view to promote captured IDs back into the workflow with one click.
Sign in to inspect routes, plans, and trips.
Sign in to inspect routes, plans, and trips.
Review forecast freshness, worker heartbeat, runtime health, and trigger a manual sync with justification when needed.
Run the read paths most operators need during staging validation and live troubleshooting.
Prefer the portal and documented operator APIs over ad hoc shell access so support actions stay accountable.
Read the health summary first, then drop into the raw payload when you need backend detail.
Sign in to inspect forecast and ops state.
Sign in to inspect forecast and ops state.
Provision and mutate operator accounts from the same audited service layer the CLI uses, then bootstrap MFA for the current browser session.
List existing operators or create a new account with a bundled scope set.
Capture a target operator and mutate scopes, password, or TOTP state.
Bootstrap or verify TOTP for the currently signed-in operator session.
Creation, scope changes, password rotation, and TOTP bootstrap all flow through this workspace.
Sign in to inspect operator accounts and admin access.
Sign in to inspect operator accounts and admin access.
Own every operator-managed message that ships into the apps: legal copy, splash creative, feature flags, sponsored pins, disclosure rules, and runtime campaign inventory.
Use markdown or plain text for canonical operator-managed documents instead of relying on remote HTML at render time.
Control the launch surface advertisement or editorial campaign completely from admin, including artwork, CTA routing, disclosure copy, and schedule windows.
Toggle product intent here while letting the backend keep the final effective state honest when a capability is unavailable.
Define sponsored or informational placement sets, audience rules, schedule windows, and disclosure copy before attaching individual markers.
Attach individual placements to a set with coordinates, image constraints, detail copy, and CTA metadata that the clients can render in a modal sheet.
Load impression, tap, detail-open, and CTA-open metrics per set so operator support and customer reporting share the same audited source of truth.
Operator-managed launch slots, flags, documents, and map-marker inventory are summarized here before falling back to raw JSON.
Sign in to inspect campaign content, launch slots, and runtime flags.
Sign in to inspect campaign content, launch slots, and runtime flags.
Query app telemetry and managed-marker engagement with the same backend analytics contracts, then export grouped or event-level snapshots for reporting.
Use CSV fields for multi-value filters. Grouping accepts up to four dimensions such as day,eventName,surfaceID.
Jump into common queries for release validation, pin reporting, and field-surface engagement without rebuilding the query every time.
Grouped metrics, unique sessions, and export-ready event rows appear here after every query.
Run an analytics query to inspect app or advertisement telemetry.
Run an analytics query to inspect app or advertisement telemetry.
Inspect registered devices, preview typed APNS payloads, dry-run sends, and test real delivery from the same backend operator surface.
Resolve a local user first, then filter by push environment, platform, or token suffix before sending.
Compose a reusable typed payload, preview it first, then either dry-run or send it to matched devices or a direct token.
Resolved devices, APNS previews, and delivery results are summarized here before falling back to raw JSON.
Look up a user’s devices or preview a payload before sending.
Look up a user’s devices or preview a payload before sending.
Filter immutable operator events by action, target, operator, or status to confirm what happened and why.
Use the current shared context to focus the feed on the operator, user, or route you are actively working on.
Recent operator actions, targets, status, and captured justification.
Sign in to load the operator audit log.
Sign in to load the operator audit log.