Admin Console Tour
Admin Console Tour
Section titled “Admin Console Tour”The admin console is the browser surface for control-plane work. It does not replace the runtime gateway, CLI, or contracts. It organizes onboarding, approvals, policy, credentials, sessions, audit, topology, and settings around the same product boundaries used by the backend.
Audience
Section titled “Audience”- Platform admins finding the route for a governed source, policy, credential, or session task.
- Security reviewers checking which UI surfaces are backed by current routes.
- Operators separating route-backed pages from placeholder shell sections.
What is this?
Section titled “What is this?”This page maps the current React routes and AppShell navigation to docs sections. The UI is served by apps/ui, routes live in apps/ui/src/App.tsx, and product shell navigation lives in apps/ui/src/components/layout/AppShell.tsx.
Current grouped surfaces:
| Group | Current UI surfaces | Use |
|---|---|---|
| Overview | /overview | Shared operator starting point. |
| Govern | /approvals, /mcp-servers, /api-sources, /agents, /catalog-lite | Review submitted capabilities and inspect governed sources. |
| Access | /policies, /credential-bindings, /client-surfaces | Author policy, simulate decisions from a policy detail tab, bind credentials, and scope callers. |
| Operate | /deployment-status, /data-planes, /connectors, /active-sessions, /audit-export | Inspect runtime state, routes, sessions, and export posture. |
| Investigate | /audit-search, /deny-diagnostics, /admin-activity | Search audit metadata and explain denied calls. |
| Settings | /identity-provider, /role-bindings, /local-identity, /environments, /settings/telemetry, /settings/siem-webhooks, /license | Configure identity, RBAC, scope, telemetry, SIEM, and license read models. |
The registration wizard for MCP servers is route-mounted at /onboarding/register-mcp-server. API source import is route-mounted at /api-sources/import.
When do I use it?
Section titled “When do I use it?”Use the console when a human needs to submit, review, approve, inspect, disable, revoke, or diagnose a gateway resource. Use the CLI or Admin API when the same workflow needs scriptable proof, generated references, or CI evidence.
What happens?
Section titled “What happens?”- The app authenticates non-public routes through the auth boundary and reads identity from
GET /v1/identity/me. - AppShell renders the sidebar, route highlight, search affordance, shortcuts, theme controls, account menu, and emergency-disable entry point.
- Dedicated routes own list/detail workflows for MCP servers, API sources, agents, policies, credential bindings, connectors, sessions, audit search, data planes, identity, role bindings, local identity, environments, telemetry, and SIEM/webhooks.
- Placeholder shell sections currently mount the shared dashboard page until their dedicated surfaces are swapped in.
- UI contracts and runbooks keep page behavior tied to Admin API, CLI, fixtures, permissions, and metadata-only rules.
What can go wrong?
Section titled “What can go wrong?”- A route may exist before its deep workflow page is fully wired. Treat placeholder shell content as route coverage, not proof of a completed feature.
- Auth failure blocks non-public pages before product work starts.
- A user may see no mutation action because collection or resource permissions deny it.
needs-source: exact public docs for every per-route empty state are not complete yet. Use the route code and UI contract docs until U8 verifies each story.- UI evidence must not be replaced with raw screenshots or private payloads in public docs.
Source truth
Section titled “Source truth”- Read Register an MCP Server for the server submission and approval model.
- Read OpenAPI-to-MCP for API source import.
- Read Identity, Policy, Credentials for the access checks behind the console.
Type set in Geist, Source Serif 4, and Departure Mono.