Overview
The end-to-end path in the platform, from the environment base to daily operations, and who does each part.
The Concepts section explains what happens in a tool call. This section shows how to get there through the Admin: what the administrator configures, what the agent developer does and what the administrator follows afterwards.
The work has five stages. The first two belong to the administrator and happen before any call. The third belongs to the developer. The fourth is use, which nobody needs to operate. The fifth returns to the administrator.
| Who | Does | Where |
|---|---|---|
| Administrator, once per environment | Identity provider, MCP servers, tool review, context sources | Identity providers, MCP servers, Context sources |
| Administrator, per agent | Create, generate the key, delegation, tools, rules, publish | Agents |
| Developer | Puts the key in the agent; a customer MCP server validates the token | Developer integration |
| Person or service | Signs in to its own IdP, as today | — |
| Administrator, daily | Overview, Inbox, Investigate, adjustments, kill switch | Operations |
The examples in this section use an environment with two MCP servers, Acme Issues and Acme Billing, and two agents: issues-manager, which works on repository issues, and refunds-assistant, which looks up orders and issues small refunds.