Summary

Customers require full visibility of Atlassian Rovo usage events (e.g., "Start Rovo Chat") within the organization's Audit Logs.
Currently, Rovo activity is not consistently captured in the Atlassian Administration Audit Logs. This prevents organization admins from accurately monitoring/auditing AI usage across their workforce.

Suggested Solution

1. Audit Log Parity - Ensure all Rovo interactions (starting chats, agent usage, etc.) are reliably logged in the organization Audit Logs with the associated user identity.

1. Granular Reporting: Ensure usage data includes specific user identifiers (AAID/Email) to facilitate per-user compliance checks.