Skip to main content

Usage Metrics

Monitor how AI platforms are being used across your organization to understand patterns and tune policies.

note

Per-user AI usage reporting is partly roadmap work. The dashboard's alert and policy analytics ship today; the per-user request/service columns are wired to a usage source that is not yet populated, so they render 0 and "No activity" for every user. This page marks each surface as available today or planned.

Available Today​

Overview Analytics​

The overview dashboard is the shipped analytics surface:

SurfaceDescription
Open alerts / Total alertsOutstanding alert volume
Active policiesEnabled policies, "N of M enabled"
ExtensionsExtension coverage across devices
Blocked todaySubmissions blocked today
Alerts trendAlert volume over time
Policy coverageDistribution of enabled policies by category

Per-User Signals​

On the Users page, each user row and detail drawer carries:

  • Devices — registered device count
  • Alerts — violation count attributed to the user (or Clean)
  • Last active, Invited, Activated — activity and lifecycle timestamps
  • Registered devices — the user's device list

Audit-Event History​

The Activity page provides the metadata-only event timeline — policy changes, alert actions, violations, and device events — filtered by tab, date range, and search.

Monitored Platforms​

The extension monitors these AI chat surfaces:

  • ChatGPT (chat.openai.com, chatgpt.com)
  • Claude (claude.ai)
  • Google Gemini (gemini.google.com)
  • Microsoft Copilot (copilot.microsoft.com)
  • Grok (grok.com)

The monitored platform set is fixed in released extension versions. Adding AI chat front-ends (including enterprise-internal ones) via the planned allowedDomains managed-storage key is a roadmap capability — released versions do not yet read managed storage.

Discovering Unsanctioned Tools​

The first time a new AI tool is seen in your organization, an informational alert is recorded. See Understanding Alerts.

Planned Reporting​

note

The following are not shipped. There is no usage-analytics page, and none of these surfaces exist in the product today:

  • Per-user session, message, and token counts (the Users page's Usage and Requests figures are the placeholder for this and currently read 0)
  • Usage-over-time, platform-distribution, and top-users charts
  • A usage heatmap by hour and day
  • DAU / WAU / MAU rollups
  • Filtering usage by team or user type
  • Per-chart export to CSV, PDF, or PNG
  • Scheduled reports (there is no Settings > Reports screen)
  • Anomaly detection on usage volume or off-hours activity

If per-user AI usage reporting is a requirement for your deployment, contact your account manager so we can scope what is available for your environment.

Export Today​

The only data export in the product is on the Activity page — audit events as JSON Lines or CSV, available on Enterprise plans. It covers audit events, not alerts or usage metrics.

Understanding the Metrics​

Alerts per User​

A user's alert count reflects policy violations attributed to them. High counts may indicate either risky behavior or an over-broad policy — check a sample of the alerts before concluding which.

Devices per User​

Users legitimately have multiple devices (for example Chrome and Edge on one laptop). Compare device counts against your rollout expectations to spot unprotected users.

Last Active​

Use Last active to identify users who have stopped generating activity — often a sign the extension was removed or the user signed out.

Best Practices​

Regular Review​

  • Review alert volume and trend weekly
  • Investigate sudden changes in Blocked today
  • Track extension coverage as you roll out

Policy Alignment​

  • High alert rates may indicate policy tuning is needed
  • Low activity may indicate an adoption or installation problem
  • Use Policy coverage to spot categories with no enabled policies

Privacy Considerations​

  • Alert records retain violation metadata and a redacted prompt excerpt, not the full prompt
  • Audit events are metadata only
  • Individual user data is visible to administrators and is subject to your organization's retention window