You must be an Owner in your Claude organization to open the Audit page; the other trails on this page are visible to anyone with access to the underlying surface.
- The Audit page in admin settings, with tabs for scheduled work, memory, and (if enabled) network events
- Memory files on each scope (select the scope in the Claude Tag’s access section, then choose View memory files from its ⋯ menu), where you can review what Claude has saved
- Attribution on each action Claude takes in a connected tool
- The audit logs of each connected service, where its actions appear under the service account you provisioned
What the Audit view lists
The Audit page, labeled Activity in the admin console’s left nav and page heading, atclaude.ai/admin-settings/claude-tag/audit has these tabs:
Each routine on the Scheduled work tab shows Created by (the member who set it up) in its View details dialog. There is no per-action log of every task and who asked; for that, use the trails below.
Trace an action to its source
In channels, Claude acts as itself, so each action there carries the service-account identity:- In Slack, it posts as the Claude app, and its work happens in threads anyone in the channel can read.
- On code, commits and pull requests show the Claude GitHub App as the author, and each one links back to the Slack thread it came from.
- In every other connected service, actions appear under the service account you created for the connection.
See what’s scheduled in a channel
Anyone in the channel can see its standing work. Ask in the channel:Related resources
- How agent identity works: how attribution differs in channels and DMs
- Restrict where Claude Tag operates: the controls when an audit turns something up
- Security and data handling: the model behind the trails