Using the product

Operations & admin screens

Discovery and Integrations for connector health, Analyze IaC for ad-hoc analysis, and the Admin Portal with a ledger-anchored audit trail.

The Operations group keeps your connectors healthy and lets you analyze IaC on demand; the Admin Portal runs the account and proves every privileged action.

Discovery

/discovery · reads GET /api/discovery/overview, GET /api/discovery/events

A real-time observation view: connected sources on the left, a recent-activity feed on the right built from real events (scan completed/failed/running, identity discovery, audit-log actions). It re-polls every 30 seconds; Pause polling pauses real polling — it is not a synthetic stream.

Integrations

/integrations · reads GET /api/discovery/overview

The connector-health surface, grouped by Cloud, Source control, and CI/CD. Tiles summarize healthy and degraded/paused connectors, identities surfaced, and last scan; each row shows a real status (healthy / degraded / disconnected / paused). There are no invented metrics — a never-checked connector reads "not checked," not "ok."

Analyze IaC

/analyze

Ad-hoc analysis with no connected account needed. Paste Terraform, an IAM policy (JSON), or CloudFormation (YAML) and click Analyze; format is auto-detected. You get one of three honest outcomes — a verified fix (with before/after diff and confidence), "couldn't safely auto-fix," or detection-only. This V1 surface is carried into the V2 shell because there is no V2-native equivalent.

Admin Portal — NEW

/admin-portal · reads GET /api/admin/portal/*

A single console for running the account and proving every privileged action. Access is gated server-side (at least the ADMIN org role), and every underlying API re-checks the role against the database on each call — no session-claim trust.

Its differentiator is a ledger-anchored audit trail: each privileged action is written to the tenant audit log and anchored as a signed entry in the Trust Ledger, so an insider can't silently edit or delete their own tracks. The portal's sections include:

• Overview — org and role summary plus a live "Ledger integrity" badge (a real chain verification), with every figure real or an honest empty.
• Audit Trail — the ledger-anchored feed; anchored rows carry a Verify ledger button that re-checks the Merkle inclusion proof live; un-anchored rows are labeled "AuditLog only."
• Members & RBAC — the member roster and role changes (OWNER-only, confirm-stepped, and refusing to demote the last OWNER). See the security model for the role matrix.
• Account & Plan — org profile, effective plan limits and feature flags, and usage. Subscription self-service (Stripe checkout/portal) lives on Billing & Plan (/billing).
• Security · SSO — per-tenant SAML 2.0 / OIDC mapping and optional SSO-only enforcement (OWNER-only, entitlement-gated). Linked from Enterprise Settings.
• API Keys — mint least-privilege scoped keys; the plaintext token is shown exactly once and only its hash is stored. See the API reference for scopes.
• Data Export — generate a signed SOC 2 evidence bundle via a time-limited signed URL (entitlement-gated).

The customer-facing record of your own team's actions lives separately at /audit-log; the Admin Portal trail is the admin-level, ledger-anchored one.