Admin access and operations overview

Enter the restricted admin realm and inspect platform health.

Last updated: 9/10/2026

Enter platform operations

Admin authentication uses a separate realm and grants no authority over customer funds.

01

Sign in as the operator

Open 127.0.0.1:3101 and choose Sign in with development wallet (admin-auth-continue). Only the seeded operator identity can enter /operations.

02

Use the operations navigation

Open Overview, Integration proofs, Organizations, Failed jobs, Support, or Settings through admin.nav.*. Use admin.nav.toggle on small screens and admin.auth.sign-out to leave the realm.

Admin development-wallet sign-in screen
The admin entry uses a separate authentication realm and local simulation warning.

Read platform status

Overview counts and health come from stored platform records rather than presentation fixtures.

03

Review counts

On /operations, read admin.overview.status and the organization, analysis, payment, reconciliation, and support counts under admin.overview.*. Use the matching Inspect links (admin.overview.inspect).

04

Handle a read failure

When a count query fails, the page shows an alert and Retry counts (admin.overview.retry). It does not show stale success alongside an error.

05

Read service health

Current service health projects supported providers, collapses duplicate instances by active release, and keeps expired heartbeats in history.

Admin operations overview with counts and current service health
The overview gives operators a typed summary before they enter an investigation.