# The admin dashboard

> A web console for operating a cluster of agents — live sessions and tool calls, pending approvals, configuration, and the audit trail.

Source: https://openap.org/docs/admin-dashboard

Beyond talking to one agent, someone has to *operate* the fleet — see what's running, who's waiting on
an approval, what each agent is configured to do, and what it did. That's the **admin dashboard**:
a web console served by the platform, gated by the same authorization graph as everything else.

[Video: A walkthrough of the real admin dashboard — Overview, live sessions, approvals, the agent config, tiered settings, and the audit log.](https://openap.org/media/admin-tour.mp4)

## What it shows

The console groups its views by what you're doing:

- **Live** — agent **sessions** in flight, **live tool calls** as they happen, pending **approvals**, and
  active work.
- **Config** — the **agents**, **tools**, **skills**, **sources**, **channels**, and **identity** wiring, plus
  **users**, **access**, and tiered [**settings**](https://openap.org/docs/settings-config). It's where you review what an agent is
  allowed to be.
- **Audit** — the **logs**, past **sessions**, **budget** and spend, **artifacts**, and the **memory** and
  **knowledge** stores. This is the read side of the [tamper-evident record](https://openap.org/docs/audit-log).

## Each section in depth

- **[Live activity](https://openap.org/docs/admin-activity)** — sessions in flight, live tool calls, and the approvals queue.
- **[Agents, tools & skills](https://openap.org/docs/admin-agents)** — the reviewed building blocks of an agent.
- **[Channels & directory](https://openap.org/docs/admin-connectivity)** — where agents are reached, and the directory syncs.
- **[Identity, users & access](https://openap.org/docs/admin-identity)** — who acts, whose credentials, and who administers.
- **[Memory, knowledge & artifacts](https://openap.org/docs/admin-memory)** — the stores agents write to and produce.
- **[Audit log & budget](https://openap.org/docs/admin-audit)** — what happened, and what it cost.

Config also includes the tiered [Settings](https://openap.org/docs/settings-config), shown in the console per setting.

## Reached like any other surface

The dashboard is a loopback-only tab on [Desktop](https://openap.org/docs/install-desktop) and a signed-in, authorized surface on a
cluster — the same [sign-in](https://openap.org/docs/idp-signin) and per-request SpiceDB checks as the browser chat. Being an admin
is itself a permission in the graph, not a static role file, so who can see and change what is answered the
same way as who can call a tool.

> **Security: Acting through the console still runs the guards**
>
> Installing an agent, approving a step, or changing config from the dashboard runs the same choke-point checks
> as doing it from the CLI — the console is a front end to the governed platform, not a side door around it.
