Identity should be interpreted, not just listed
Known, automation, and unresolved accounts need visibly different treatment on the category page.
QI
Users Category View
User inventory should answer who is trusted, who is unresolved, and whose work carries the most company consequence before it behaves like a directory.
Use This Page When Asking
Who is well understood, who is unresolved, and whose work carries the most consequence?
Users observed
12
Human and automation mixed
Unknown identities
1
Trust gap still open
High-spend users
2
Most cost is concentrated
Strongest baseline
developer lanes
Known hosts and tools
Why This Page Exists
What This Page Should Make Obvious
User meaning comes from surrounding context
Preferred agents, keys, hosts, and spend shape whether a person is routine or worth review.
Keep endpoint adjacency close
A user without their machine context is harder to judge quickly.
Fastest Drill Paths
Known developer baseline
A representative human user with a stable host and repeated stack preferences.
This gives the operator a baseline for judging outliers.
Unknown identity lane
One unresolved user still affects confidence in the surrounding inventory.
The raw list should remain a quick way to find that open trust gap.
User-Centered Topology
A user map should show identity, spend, preferred stack, and where anomalous activity branches off.
Useful per user: role, session volume, cost, primary agent/model, machine footprint, credentials used, and whether the identity is human, CI, or unresolved.
User
bob@company.com
High-spend developer profile with a strong preference for Cursor plus claude-opus-4-6.
4 sessions · $12.40 total
Role
developer
Primary agent
Cursor v0.42.0
Primary model
claude-opus-4-6
Identity posture
known account
Identity
How this user should be understood by platform and security.
developerrole
qpoint-devorg context
bob-thinkpad.localprimary host
Preferred Stack
The recurrent choices this user makes.
Cursor v0.42.0agent
claude-opus-4-6model
sk-ant-...A3F2credential
Activity Shape
The work pattern behind the spend.
31 turnslargest live session
$8.20top single session
1h 12mlongest session
Risk Lens
What makes this identity worth attention.
outlier spendabove org avg
unknown peerscompare against unknown users
session driftwatch for new hosts
c6 Raw Reference
Users observed
12
Unknown identities
1
Trust gap
Top user
alice@company.com
Primary lane
Claude Code
Why Keep The Raw Ledger
Open c6 Raw List
Use the original category ledger for exact rows, counts, and timestamps.
Open c6 raw listRaw User Inventory
Identity, role, sessions, spend, and primary tools.
| User | Role | Sessions | Total cost | Primary agent |
|---|---|---|---|---|
| alice@company.com | engineer | 6 | $2.41 | Claude Code |
| unknown | unmapped | 1 | $0.61 | Claude Code |
| ci-runner-04 | automation | 11 | $0.82 | LangChain |