← c12c12 / wf1 - Inventory Deep Dive / Inventory / Users / Detail
Qpoint
QI
Inventory /Users/alice@company.com

Users Detail

A user detail page should connect identity, preferred stack, machine footprint, and notable activity patterns into one readable operator profile.

The detail should make it easy to tell whether this is an ordinary human, an automation lane, or a partially unresolved identity story.

Use This Page When Asking

Is this operator profile well understood, or is there enough identity or behavior drift to keep it elevated?

Open c6 raw detail

Sessions

6

Recent work volume

Primary agent

Claude Code

Repeated software lane

Primary endpoint

alice-mbp.local

Stable host context

Spend posture

within band

Not the main outlier

Why This Detail Matters

This detail should make one users story readable end to end before the reviewer drops into raw evidence tables.

Important Metadata

Identity should become clear before relationship context and sequence take over.

Email

alice@company.com

Role

engineer

OS Username

alice

Account ID

acct_01AbcXyz...

Organization

qpoint-dev

Primary Agent

Claude Code

What This Detail Should Help Decide

The page should leave the reviewer with a concrete next move, not just more context.

Compare the user to the unresolved identity lane

The page should help reviewers contrast strong identity baselines with weak attribution cases quickly.

Check whether new hosts fit the established profile

Unexpected endpoint spread should be easier to spot than it is in the raw directory view.

Use sessions as evidence, not as the page title

The detail page should stay centered on the user profile rather than collapse into a recent-sessions table.

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.

3 nodes
developerrole
qpoint-devorg context
bob-thinkpad.localprimary host

Preferred Stack

The recurrent choices this user makes.

3 nodes
Cursor v0.42.0agent
claude-opus-4-6model
sk-ant-...A3F2credential

Activity Shape

The work pattern behind the spend.

3 nodes
31 turnslargest live session
$8.20top single session
1h 12mlongest session

Risk Lens

What makes this identity worth attention.

3 nodes
outlier spendabove org avg
unknown peerscompare against unknown users
session driftwatch for new hosts

Representative Event Chain

The page should show how the item participates in a readable sequence, not just a pile of supporting rows.

4 steps
  1. 1

    Identity

    The page establishes who this person is in the organization

    Role, organization, and account mapping should immediately tell the reviewer whether this is a human baseline or something less certain.

    alice@company.comdeveloperqpoint-dev
  2. 2

    Preferred stack

    Repeated agent, model, and key choices make the user legible

    The preferred stack gives the reviewer a fast baseline for what normal work from this person looks like.

    Claude Codeclaude-sonnet-4-6sk-ant-...A3F2
  3. 3

    Activity shape

    Session size and endpoint spread reveal whether behavior is drifting

    Long sessions, high cost, or new hosts matter more when they break from the user’s usual pattern.

    6 sessionsalice-mbp.local1h 12m
  4. 4

    Investigation pivot

    The reviewer moves into sessions or endpoints only after the operator profile is clear

    The raw rows remain important, but the page should already explain the person-shaped pattern they belong to.

    sessionsendpoints

c6 Evidence Tables

These are verification surfaces after the story is understood, not the first read.

Sessions

The raw detail keeps recent runs tied to endpoint and model.

AgentEndpointModelStartedCost
Claude Codealice-mbp.localclaude-sonnet-4-614 min ago$0.43
Claude Codealice-mbp.localclaude-sonnet-4-64 hr ago$0.87
Cursoralice-mbp.localclaude-opus-4-6yesterday$1.11

Endpoints

c6 pairs the user with the machines they actually use.

HostnameOSTypeSessions
alice-mbp.localmacOSdeveloper6
10.0.1.44macOSunknown1

Return To Category

Compare this representative detail against the full category framing and drill targets.

Open Users overview

Open c6 Raw Detail

Use the original detail page for exact raw evidence after the c12 story framing.

Open c6 raw detail

Open c6 Raw List

Compare this item against the broader c6 entity ledger once the representative story is clear.

Open c6 raw list