Review team AI activity
Review captured AI activity and estimated spend by team while keeping attribution, visibility, and coverage in context.
What the team view shows
Open Teams, choose a team, and confirm the reporting window. Follow a person or session to inspect the underlying activity.
The 8 members shown in the screenshot is the roster count, not the count with captured activity. Last captured shows when activity was last captured. Adoption counts people with activity in the selected window; estimated spend prices captured usage in that scope. A configured budget does not verify enforcement.
How attribution works
Cortex Defender uses the signed-in person; Egress Gateway uses the personal capture token. The resolved person's primary team supplies reporting context. Visibility controls which people and teams appear; unresolved identity remains unattributed.
Team reporting does not assign workstream ownership or grant access. See People, teams, and ownership.
Interpret a gap
| Signal | Check next |
|---|---|
| No activity | Coverage, date range and visibility. |
| Unattributed | Sign-in and organization identity. |
| Sudden drop | Reporting devices and enabled sources. |
| Concentrated usage | User profiles and the work behind the total. |
Activity and spend describe captured use, not employee output or performance. Use work units to inspect evidence and roles/visibility for access.