Skip to content
English
  • There are no suggestions because the search field is empty.

A user's AI activity isn't showing

Summary

You expected to see someone's AI usage and the timeline looks empty or incomplete. Most of the time this has one of four causes: the lookback window, a filter, activity that is collapsed or truncated rather than missing, or a genuine coverage gap. Check them in that order: the first three take seconds.

Before you start

Have the person's email address to hand. You'll use it on both Activity and Coverage.

Where to find a person's AI activity

There are three places, and they answer different questions:

Where What it shows
See → Activity The organization-wide timeline of every AI transaction and security event. Filter or search by the person to narrow it to them. This is the page the rest of this article refers to.
See → Users, then click the person Their own detail view, in two sections: Cyber Risk (DLP violations, behavioral anomalies, data flow map and security timeline) and AI Usage (usage profile, use-case breakdown and maturity).

Home → My AI

Your own usage only, read-only. It is not an admin view and cannot show you a colleague.

If a colleague's activity looks missing, start on See → Activity and work through the checks below. If you want everything about one person in one place instead, open them from See → Users.

1. Widen the lookback window

Activity loads a window, not everything at once. The selector offers 1h, 24h, 7d, 30d, and 90d: 90 days is the ceiling, matching event retention. If you're looking for something from last month, a 24h window won't contain it.

2. Check your filters

The Activity list tab filters by person, AI platform, source, and actor (Human, Supervised agent, Autonomous agent), plus toggle chips such as Flagged, DLP alert, Blocked, Privilege escalations and Privilege uplift. The usual culprits:

  • Actor filter: agent activity won't appear while the filter is set to Human.
  • Toggle chips: these hide ordinary activity while active.

A user search box narrows the loaded window to one person. It only searches what's already loaded, so widen the lookback first, then search. It's hidden on workspaces that de-identify activity, where it could never match.

Clear all filters and see whether the activity reappears before investigating further.

3. Check whether it's collapsed or truncated, not missing

  • Collapsed sessions. Consecutive activity to the same provider from the same device collapses into one expandable session card. A single row may contain many interactions: expand it first.
  • A truncated stream. On a busy window the ordinary-activity stream is row-capped, and a note above it says so and states how far back the loaded rows reach. When that note is showing, "looks quiet" is not the same as "was quiet": narrow the window or filter to the person you're after.
  • Pinned rows. Incidents and privilege changes sit separately from the main stream, so they aren't where you'd expect them chronologically.

Data-loss, privilege-uplift, and blocked-policy rows ride their own lane covering the whole window, so they still appear even when the ordinary stream is capped.

4. Check how a data-loss hit is labeled

Detections are shown at two confidence levels and counted separately: an alert is a high-confidence, actionable hit; a signal is a lower-confidence hit below the alerting threshold. Both appear on the summary tiles, chips, session cards, and row badges. If you check only alert counts, a real but lower-confidence hit reads as zero.

5. Check the person is actually covered

Someone no sensor reaches is invisible to DLP and every other detection: nothing was missed, nothing was captured.

Go to Coverage → Action needed and look for the person. The filter chips name the gap:

  • No extension: nothing reaching them at all; the likeliest cause of a completely empty timeline.
  • Personal device: a personal device, harder to instrument. This chip shows only while an older personal-device gap is still open.
  • Stale: a sensor installed but no longer reporting. See An endpoint sensor isn't reporting.

The Action needed queue is part of the Professional and Ultimate plans. On Starter, go to Coverage → Overview instead and, under People by coverage, select No coverage or Partial coverage: each opens the Users list filtered to the people in that state.

Partial coverage produces exactly what you're seeing: some activity, not all of it.

6. Check what your coverage type can and cannot see

  • Clipboard activity, running processes, installed software, and privilege events come only from the endpoint sensor. With the browser extension alone, these never appear.
  • Response-content capture is best-effort, so a record may carry less detail than expected.
  • Private or incognito browsing may not be reported.
  • One platform missing but others fine: capture health shows a per-platform status grid (where it is enabled for your organization). An extension installed outside the browser's store also needs explicit site-access permission, or it captures nothing.

Confirm it's resolved

Clear all filters, set a window you know contains activity, and confirm the person's entries appear.

Related