Claude Platform Docs
AdminAccess Transparency

Access Transparency

Receive an audit record of human access to your organization's data by Anthropic personnel through the Compliance API.

Learn how Access Transparency creates a record of human access to your organization's data by Anthropic personnel, what it covers, and how to receive events through the Compliance API.

How Access Transparency works

Anthropic personnel access customer content only under defined conditions. Access Transparency is designed to make such access visible to you. The design rests on the following principles:

  • Human access happens only under a published reason code.
  • Human views of your covered content are recorded. Anthropic's internal tooling that can reach your covered content is instrumented to emit an event on each view.
  • Events represent human access, not automated processing. Anthropic's automated safety systems process your content in a secured pipeline with no interactive human access; that processing does not generate anthropic_access events. The one event automated processing can initiate is a cmek_preserve preservation record (see CMEK content preservation).
  • Events arrive on your existing feed. Activities are accessible through your Compliance API Activity Feed. Existing credentials, audit, export, and SIEM integrations for the Compliance API still apply.
  • Events are tamper-evident. Each event recorded after your organization's transparency log (beta) is created is also committed to that log. The log is an append-only, signed record that you can verify independently of Anthropic's serving systems.

What Access Transparency covers

  • Covered content: Access Transparency covers prompt and response content sent through the Claude Messages API or Claude Code sessions. Anthropic's general ZDR documentation explains which APIs and features are covered by ZDR. The same APIs and features are covered by Access Transparency.
  • Manual views by Anthropic personnel: Manual views of your covered content by Anthropic reviewers generate events.

What Access Transparency does not cover

  • Automated processing: Model serving, safety classifiers, and abuse-detection pipelines process your content as part of normal operation and do not generate anthropic_access events. Preservation initiated by automated processing does generate a cmek_preserve event (see CMEK content preservation).
  • Your own organization's activity: Your API calls, admin actions, and Compliance API reads are covered by standard