Skip to main content

Find your way around

The Console is where you operate your Kilimanjaro projects from a browser. It's organised around five modes — Workspace, Studio, Forge, Vault, and Admin — each one tuned to a different kind of work. You switch between them from the mode picker at the top of the screen.

The mode you land in first depends on your role. The mode picker only shows the ones you have access to.

The five modes​

Workspace — get work done.

If you're a business user filling out forms, reading dashboards, and using views your team built for you, you're working in Workspace. It's the consumption surface; everything in it was designed for you in Studio.

Studio — design the experience your team uses every day.

If you're composing Views, building Forms, drawing Workflows, designing Dashboards, or authoring identity flows for end users, you're working in Studio. Studio is for business-team authors (the platform calls them Pathmakers) who shape what other people see.

Forge — build on the platform.

If you're writing migrations, browsing collections, querying data, deploying functions, or installing extensions, you're working in Forge. This is where developers spend most of their time.

Vault — operate your encryption custody.

If you're rotating keys, managing secrets, browsing the signed audit ledger, or moving custody between Platform-Managed, SKR, BYOK, and HYOK, you're working in Vault. Vault is the operational surface for the platform's custody primitives.

Admin — govern the project.

If you're inviting people, configuring an identity provider, reviewing the audit log, setting up Maker-Checker approvals, or managing policies, you're working in Admin. The Admin Watchtower also surfaces a thin Vault oversight summary; actual custody operations live in Vault mode.

The five-mode order — Workspace → Studio → Forge → Vault → Admin — reads as depth of access: from everyday consumption at one end to governance at the other.

Where you land when you sign in​

Different people land in different places. The Console picks based on your role:

  • Business users land in Workspace, on a Briefing dashboard for the workspace you most recently used.
  • Pathmakers land in Studio, on the last surface you were authoring.
  • Developers land in Forge, on the Workshop dashboard.
  • Project admins land in Admin (or Vault on a Kibo-only project), with last-visited-mode persistence within the session.

If your sign-in URL was a direct link to a specific surface (someone shared it with you, or you bookmarked it), the Console takes you there instead. The mode-picker remembers your last choice per browser tab, so opening two tabs in different modes is fine.

What if I only have Kibo?​

Kibo customers — the standalone secrets-management module — see only Vault mode in their mode picker. The other four modes are hidden because they don't apply. The Settings pillar remains visible at the appropriate scope. To Kibo customers, Vault mode is where they live: it's the surface that holds Keys, Secrets, Custody, Audit Ledger, and Usage.

If your organisation has both Kibo and the rest of Kilimanjaro, switching between a Kibo project and a regular project changes which modes appear — a Kibo project surfaces Vault mode as primary; a regular project surfaces all five.

URLs​

Every Console URL is shareable and reload-stable — filter state, active tabs, and pagination all live in the URL. You can hand a URL to a teammate and they'll see exactly what you see (subject to their permissions).

The shape:

<your-org>.console.k9o.io/@<your-project>/<surface>/...

Modes change the NavRail context and chrome composition, not the URL paths underneath. The same /data URL renders under Forge's NavRail when you reach it via Forge; the same /vault/keys URL renders under Vault's NavRail. Bare-mode URLs (/admin, /forge, /vault, /studio, /workspace) land on each mode's Pulse dashboard.

The platform reserves a different shape for end users your application authenticates — those run on your project's API host, not the Console. End-user sign-in lives in Gate, not here.

See also​