Choose the export scope
Enter demo mode, confirm the Demo enterprise, and open AI activity. Apply the search, AI tool, risk, evidence and sample-date filters you want. The result count shows how many rows currently match.
Select Export CSV. The file contains those matching rows from the selected fictional enterprise only. It does not combine Northstar and Meridian or export every view. If nothing matches, the app shows No matching events to export instead of creating an empty file.
What the CSV contains
The download includes summary fields for each event. The filename identifies the demo enterprise, such as aitooltracking-northstar-demo-events.csv or aitooltracking-meridian-demo-events.csv.
- id and time: event reference and its timestamp.
- user, team and device: the fictional employee and endpoint context.
- file and tool: document display name and AI destination.
- classification, risk, evidence and inspection: the event's summary states.
What stays out of the export
Investigation notes, review status, detailed detector samples, complete evidence trails and document bodies are not included. A CSV is not a backup of your whole demo workspace. To preserve a deployment draft, use its separate JSON export.
Times are exported as the stored timestamps, while the app displays UTC. If a spreadsheet application reformats them, compare the original value before interpreting a time difference. Keep the fictional-data context when sharing the file.
If the download does not appear
Check the browser's downloads area and whether downloading is blocked by your browser settings. Confirm that at least one activity row matches before trying again. The export is created in the browser; it is not emailed or uploaded to an external reporting service. Resetting a demo later does not remove CSV files you have already downloaded.