Identity & Access · Teams & Users
Who is behind the fleet — agents, cost, and risk rolled up by owner.
A problem with no owner is just a shrug. This rolls every agent's spend, risk, and open findings up to the human who owns it — so the right person can be told, budgeted, or held responsible — and surfaces the agents that answer to no one.
Bottom line
7 owners behind 8 agents. 3 agents answer to no one; 3 owners run ungoverned agents; $290.50 of at-risk spend traces to a named owner. Team rollups are projected until the directory join.
7
distinct owners
8 agents
3
agents with no owner
alias or proxy-only
3
owners w/ ungoverned agents
unbound by policy
1
owners w/ critical agents
posture < 50
No owner to hold accountable
3 agents answer to no one — a vendor alias (duck.com) or a proxy-only agent with no human behind it: Codex CLI, marketing-gpt, Zed Agent. Until they're joined to a person, their cost and risk land on nobody.
Accountability roster — by owner
7 owners · ranked by risk, then at-risk spendBy team — projected
directory join · not yet liveTeam rollups land when agents are joined to your IdP / SCIM directory. Today we observe the owner identity from telemetry; the team column above is a projected directory attribution. Once joined, this becomes spend & risk per team:
Svc-support
1 agent · $168.40
$168.40 at risk
Unattributed · vendor
1 agent · $78.00
$78.00 at risk
Unattributed
2 agents · $44.10
$44.10 at risk
Mark
2 agents · $245.50
Jane
1 agent · $96.20
Svc-data
1 agent · $52.30
Rolled up from agents by owner (email || user), joined to findings + sensitive opens + governanceTaggedSpend logic — from app/data/c16-fleet.ts. Owner is observed; team is projected until the directory join. Distinct from Showback, which ranks identities by risk-weighted spend for chargeback.