Select a row to open the inspector. Updated 12 seconds ago.

Two plots, one shared time axis — runs and latency have different units, so they never share a scale.

Recent runs

Build

Authoring: agent definitions, their test suites, and the tools they can be granted.

The left panel shows how this section subdivides. Its screens aren't part of this preview — the point here is that every section carries its own contextual panel, and the top bar stays put.

Connect an MCP server

This section only adds things. When a connection is saved its credential goes to Secrets and the server itself appears in Inventory — which is where you manage it from then on.

Platform defaults come from the deployment’s own configuration and cannot be edited here. Models added by the organisation carry their own provider key.

Secrets

Every credential this organisation holds, wherever it was entered. Secrets are sealed in an encrypted vault, and a value is never returned to the browser — not to this page, not to an administrator, not through the API. A secret can be rotated, revoked or deleted. It can never be read back.

Select a secret to rotate, revoke or delete it. Secrets are added in the flow that needs them — connecting a server, adding a model provider, configuring mail — so this page is the register, not another place to type one in.

Showing all 12 policies.

Application order

Layers compile from the outside in. A narrower layer can tighten what a broader one allows, never loosen it — so a business unit can be stricter than its organisation, and an agent stricter again, but neither can undo a rule set above them.

A role is held in this organisation. The same person can hold a different role elsewhere.