> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wardin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The Console

> Where you configure Wardin — organized into GATEWAY, PLATFORM, and ORGANIZATION sections.

The Console is Wardin's off-rail control plane — everything that **changes how
requests get handled**, as opposed to the [Request Path](/concepts/request-path) rail,
which only shows you what already happened to a request. Open it from the `CONSOLE`
button in the header, or the square node next to the six rail diamonds.

## Placement rule

Every screen in the product answers exactly one of two questions, and that answer
decides where it lives:

* **"What happened to a request?"** → a rail stage (INGRESS, POLICY, ROUTE, LEDGER,
  EVIDENCE, OUTCOMES).
* **"How do requests get handled, or what does the org offer as a capability?"** → a
  Console section.

A rail stage can still surface a **read-only glance** of a Console value — for
example, ROUTE shows the live cache similarity threshold and per-key spend — but
changing that value always happens in the Console, never on the rail.

## Console groups

Console sections are organized into three groups:

| Group            | What it covers                                                                                                 |
| ---------------- | -------------------------------------------------------------------------------------------------------------- |
| **GATEWAY**      | Everything that shapes how a request is enforced or routed in-path: keys & limits, providers, cache, webhooks. |
| **PLATFORM**     | Capabilities layered on top of the gateway: prompt registry, and future agent-facing surfaces.                 |
| **ORGANIZATION** | Tenant-level configuration: org profile, team & roles, billing.                                                |

## Shipped vs. roadmap

Every Console section is honestly labeled — a section that isn't built yet is marked
`SOON`, never presented as if it were live.

| Section       | Group        | What it does                                                  | Status  |
| ------------- | ------------ | ------------------------------------------------------------- | ------- |
| Keys & Limits | GATEWAY      | Virtual-key lifecycle, rate & spend limits, per-user caps     | Shipped |
| Providers     | GATEWAY      | Upstream credentials (BYOK), failover order, region pinning   | Shipped |
| Cache         | GATEWAY      | Semantic similarity threshold and cache decision policy       | Shipped |
| Webhooks      | GATEWAY      | HMAC-signed delivery of budget/policy/anomaly events          | Shipped |
| Prompts       | PLATFORM     | Prompt registry — versions, labels, playground, run analytics | Shipped |
| Secure Vault  | PLATFORM     | Encrypted credential store for agents and tools               | SOON    |
| MCP / Agents  | PLATFORM     | Agent-tooling gateway — scopes and tool allowlists            | SOON    |
| Exports       | PLATFORM     | Data and audit exports — S3, NetSuite, Parquet                | SOON    |
| Organization  | ORGANIZATION | Org name, default budgets, timezone, SSO status               | Shipped |
| Team & roles  | ORGANIZATION | Members, roles, SSO & SCIM provisioning                       | Shipped |
| Billing       | ORGANIZATION | Plan, invoices, payment method                                | Shipped |

<Note>
  This table mirrors the Console's own section index in the app — if a section here says
  SOON, the in-product Console shows the same dashed placeholder rather than a working
  control.
</Note>