Admin mode
Admin mode is where you govern your project. It's accessible to project admins — if you're a team member without admin access, you won't see it in the mode picker. Four clusters of work live here: bringing people on, watching what's happening, setting governance rails, and configuring the basics. The mode opens on a Watchtower dashboard — a Pulse surface tuned to operational signal an admin most often wants at a glance: recent audit-log activity, MFA enrollment across your team, pending approvals waiting on you, and a thin cross-mode summary of Vault state (key inventory, recent rotation events, next-rotation countdown) with a one-click link into Vault mode for the actual operations.
Encryption custody used to live here; it's been promoted to its own mode. If you're rotating keys, managing secrets, or moving between Platform-Managed, SKR, BYOK, and HYOK custody, you're in Vault mode now.
Bringing people onto your project
The whole journey of getting someone access — inviting them, picking how they'll sign in, putting them in the right group, deciding what they can do — lives in the Manage cluster on the sidebar.
You invite from Members, where the project's roster lives. Each person gets a role; roles range from PROJECT_VIEWER (read-only) up through PROJECT_ADMIN (full management), with specialised roles like PROJECT_AUDITOR for compliance reviewers and PROJECT_AUTHOR for Pathmakers authoring inside Studio. Change roles inline; remove people with a row action.
If you've got a lot of people, Groups lets you organise them — "the engineering team," "the finance group" — so your policies can grant access to a group rather than wiring it user-by-user.
Permissions is the read-only matrix showing what each role can do; useful as a reference when you're deciding which role someone should get.
End User Providers is where you configure how end users sign into your application. Google, GitHub, or any other OAuth flow; an enterprise OIDC connection; SAML to Okta or Entra; or AD/LDAP if you're bridging an existing directory. This is end-user identity — the people your application authenticates. Operator identity (the people who manage the Console) lives at the org level, configured under Org scope.
Watching what's happening
The Monitor cluster is how you know what's going on without having to ask.
Audit log is the unified event browser — every policy decision, every Gate event, every consequential thing that happened, with an envelope you can filter by actor, action, resource, or time window.
Rejection log surfaces every injection attempt the platform blocked, broken out by which of the four anti-injection layers caught it (SDK, edge, origin, database). Useful for spotting patterns and tuning policy.
Attributes is where you define the structured attribute tree your ABAC policies branch on — every attribute that policies will key off, with the data types and the source-of-truth resolution.
SIEM is the forwarding configuration for shipping audit events to your own observability stack — Splunk, Datadog, an HTTPS endpoint. There's a test-event action so you can verify the integration before going live.
Sessions lists the active sessions on your project, broken out by user, MFA freshness, IP, and last activity. Useful for incident response — you can revoke a session row directly.
Auth Flows audit surfaces every end-user sign-in, magic-link redemption, and OAuth callback that touched your project, with the outcome and the timing.
The Watchtower dashboard at the top of the sidebar aggregates the most-actionable items from across this cluster.
Setting governance rails
The Govern cluster covers policies, approvals, and the irreversible-action gates that protect destructive operations.
Policies lists the policies on your project, with their status (draft, published, archived). The authoring happens over in Studio → Policies; this surface is for managing the published set — open a policy to read it, validate it, publish a new version, or archive an old one.
Maker-Checker is where you configure the approval requirements for gated actions — how many approvers a gated action needs and the constraints on who may approve (for example, that the requester cannot also approve). Requirements are configured per action rather than as named reusable templates: a custody descent might require the compliance team's sign-off, a production migration two distinct admins.
Gate Approvals is the project-wide queue of in-flight irreversible actions waiting for attestation. When someone tries to do something gated, it lands here for the configured approvers to confirm or deny.
Session Policy controls how long sessions last, how fresh MFA needs to be for sensitive actions, and how many concurrent sessions per user you'll allow — bounded by the ceiling your org has set. You can always tighten past the org ceiling; you can't relax beyond it. If you try to save a value looser than the ceiling, the field flags an inline error and a banner explains which org-level limit you hit — to get more headroom, an org admin has to raise the ceiling first (see Org scope → the session-policy ceiling). If your org hasn't set a ceiling, your project policy is bounded only by the platform's hard invariants.
Irreversible Actions log is the read-only history of every irreversible-action gate that fired on your project — what was attempted, who attested it, when it completed.
Configuring the basics
The Settings cluster covers project-level configuration that doesn't fit elsewhere.
General is for display name, region (read-only after creation), and project metadata.
Notifications is where you wire up email and SMS delivery — direct SMTP, or compose with an extension like SendGrid or Twilio.
Billing carries invoices, payment methods, and the current period's running cost. The metering pipeline updates it roughly hourly.
Domain is custom-domain setup — wire console.your-domain.com to the platform's Console, and your Gate-hosted UI follows.
Vault is one click away
The sidebar carries a top-level Vault → cross-mode link. Clicking it switches the active mode to Vault — full custody operations, the signed audit ledger, secrets management, and the key inventory live there. The Watchtower Vault summary you see in Admin is a glance-only snapshot; actionable work happens in Vault mode.
If you're on a Kibo-only project
Customers using Kibo standalone don't see Admin mode — they see Vault mode as their primary operational surface, with the other four modes (Workspace, Studio, Forge, Admin) hidden in the mode picker. The Settings pillar remains accessible at the appropriate scope.
See also
- Orientation — the five modes at a glance.
- Vault — for custody operations.
- Forge — for developer work.
- Studio — for authoring policies, workflows, and identity flows.
- Org scope — for org-level operator management.
- API → Security — the audit-log + SIEM contract behind the Monitor surfaces.
- API → Control — the policy substrate behind Govern.
- API → Auth — the identity surface behind End User Providers.