Skip to content

People

Discover → AI usage → People lists everyone the endpoint collector saw in the chosen period. Pick a person to open their page: what their AI use cost, when their week happens, what they use, and the controls an administrator needs for that one person.

The people here are the account names their computers report. When an identity connector is set up, each person also shows their directory name, job title and department.

Choose the period with the time-range picker at the top right. The line above the table says how many people were seen in it.

ColumnWhat it shows
PersonThe directory name, or the account name. Beneath it: the account name (when a directory name is shown), job title and department. Select it to open the person’s page.
ComputersUp to three computers the person used, each linking to its page, and how many more.
AI tools & modelsThe AI tools and models the person used.
ActiveTime spent in applications, in hours or minutes.
AI requestsAI responses recorded for the person.
At list ratesWhat this usage would cost at the vendors’ list API prices. It is not the bill: usage a seat or plan covers costs the seat, which Overview → Home and Spend → Finance → Costs count.
Last seenThe last time one of their computers reported for them.

The list is sorted by At list rates, highest first. Select a column heading (Person, Active, AI requests, At list rates or Last seen) to sort by it instead.

The search box matches the account name, directory name, department, job title, computers and tools.

If nobody was seen, the page says so: choose a longer range, or check that the collector is installed and reporting to this environment. People appear only for the current project and environment.

The page is headed by the person’s directory name, with the account name beneath it. The bar under the heading links to each computer they used, and shows a badge for each AI tool their computers found signed in to a personal or another organisation’s account (see AI account identity). The time-range picker applies to everything on the page.

  • Directory details: what your own systems say about the person, such as Entra ID, each fact naming its source.
  • Collection for this person: lower what is collected for this person below the organisation’s collection policy: Browsing history, Shadow-AI discovery, Coding-agent content and Installed AI software. It can only narrow the organisation’s policy, never raise it. Applies now shows the level in force.
  • Microsoft 365 Copilot: the person’s Copilot use by app, shown when the Microsoft 365 Copilot connector has data for them.
  • Seats and vendor spend: the person’s seats on paid AI tools and what vendors billed for them personally, from the AI spend connectors.
TileMeaning
Actual spendTheir seats plus usage charged per token.
At API rates (not billed)What the same usage would cost with no subscription.
Plan value (not billed)The difference between the two: what their subscriptions saved over paying per token.
AI responsesResponses recorded for them.

Full cost report opens the cost report filtered to the person. This section belongs to the Finance module; without it, the section describes the module instead.

  • When the week happens: a grid for each of the person’s computers, in its own time zone. Colour is what the machine was doing, brightness is how much of the hour was in use, and an outline marks business hours. Hover a cell for what was open and how many AI requests were made.
  • Activity: headline numbers, AI responses over time by tool, and where the spend and time went.
  • Websites: the sites they visited, when your collection policy collects browsing.
  • AI in running applications: AI hostnames and on-device AI found in running applications.
  • Where their time and AI usage go: a flow chart from each of the person’s computers to tools and models (by tokens or responses), or to applications (by hours).

Selecting another person or computer in a chart opens their own page.

Export their data and Delete their data answer an access or erasure request from the person, across all of the organisation’s databases. See Export or delete one person’s data.

TaskPermission
See the list and a person’s pageView dashboards and reports (metrics.read)
See a person’s collection settingsView computers and people (collector.read)
Change a person’s collection settingsChange what is collected (collector.policy)
Export or delete a person’s dataChange what is collected (collector.policy), held for the whole organisation

People and a person’s page belong to the Security module. Every hosted organisation can read them without it, as part of Security discovery. The AI cost section and vendor spend need the Finance module.