access-transparency changedmanage-claude/access-transparency
Nearest release: v2.1.284, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+28added
Lines−18removed
From line
22
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 22, old and new numbered
/
from line 22
2222* **Human access happens only under a published reason code.**
2323* **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.
2424* **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](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation)).
25* **Events arrive on your existing feed.** Activities are accessible through your [Compliance API Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed). Existing credentials, audit, export, and SIEM integrations for the Compliance API will still apply.
25* **Events arrive on your existing feed.** Activities are accessible through your [Compliance API Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed). Existing credentials, audit, export, and SIEM integrations for the Compliance API still apply.
26* **Events are tamper-evident.** Each event recorded after your organization's [transparency log](https://platform.claude.com/docs/en/manage-claude/access-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.
2627
2728## What Access Transparency covers
2829
from line 76
7576
7677Each `anthropic_access` activity carries the standard Activity fields plus the following:
7778
78| Field | Type | Description |
79| ------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
80| `id` | string | Unique identifier for this activity |
81| `accessed_at` | RFC 3339 string | When the access occurred. Might be earlier than when the activity becomes visible in your feed |
82| `created_at` | RFC 3339 string | When the activity became visible in your feed |
83| `actor` | object | Always `{ "type": "anthropic_actor", "email_address": null }`. Individual employee identity is not disclosed |
84| `accessor_department` | string | The Anthropic team that performed the access (for example, `Safeguards`) |
85| `reason_code` | enum | See [Reason codes](https://platform.claude.com/docs/en/manage-claude/access-transparency#reason-codes) |
86| `resource_details.type` | enum | A resource type, currently only `message`. Extensible for future resource types |
87| `resource_details.id` | string or null | Identifier of the content accessed |
88| `resource_details.parent` | string or null | Identifier of the content's parent, for example the conversation ID containing a message. Currently `null` or omitted until resources with parents are supported |
89| `organization_id` | string | The organization the content belongs to. Tagged ID format (`org_...`) |
90| `organization_uuid` | string | The organization the content belongs to. UUID format |
91| `workspace_id` | string or null | The workspace the content belongs to |
79| Field | Type | Description |
80| ----------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
81| `id` | string | Unique identifier for this activity |
82| `accessed_at` | RFC 3339 string | When the access occurred. Might be earlier than when the activity becomes visible in your feed |
83| `created_at` | RFC 3339 string | When Anthropic recorded the event. An event usually becomes visible in your feed shortly after; see [Timing](https://platform.claude.com/docs/en/manage-claude/access-transparency-log#timing) for when it can lag |
84| `actor` | object | Always `{ "type": "anthropic_actor", "email_address": null }`. Individual employee identity is not disclosed |
85| `accessor_department` | string | The Anthropic team that performed the access (for example, `Safeguards`) |
86| `reason_code` | enum | See [Reason codes](https://platform.claude.com/docs/en/manage-claude/access-transparency#reason-codes) |
87| `resource_details.type` | enum | A resource type, currently only `message`. Extensible for future resource types |
88| `resource_details.id` | string or null | Identifier of the content accessed |
89| `resource_details.parent` | string or null | Identifier of the content's parent, for example the conversation ID containing a message. Currently `null` or omitted until resources with parents are supported |
90| `organization_id` | string | The organization the content belongs to. Tagged ID format (`org_...`) |
91| `organization_uuid` | string | The organization the content belongs to. UUID format |
92| `workspace_id` | string or null | The workspace the content belongs to |
93| `workspace_uuid` | string | The workspace the content belongs to. UUID format. Present when the access was scoped to a workspace, and absent otherwise. Not one of the transparency log's [leaf fields](https://platform.claude.com/docs/en/manage-claude/access-transparency-log#how-an-event-becomes-a-leaf), so an inclusion proof does not cover it |
94| `transparency_log_leaf_index` | integer | The event's zero-based position in your organization's transparency log (beta). Present whenever the event has a leaf, and absent otherwise. See [Verify Access Transparency events with the transparency log](https://platform.claude.com/docs/en/manage-claude/access-transparency-log) |
9295
9396Example JSON message:
9497
from line 106
103106 "resource_details": { "type": "message", "id": "msg_1234ABCD" },
104107 "accessor_department": "Safeguards",
105108 "reason_code": "safety_review",
106 "organization_uuid": "5b236db4-3fb4-4bf3-a560-b5e266038a15"
109 "organization_uuid": "5b236db4-3fb4-4bf3-a560-b5e266038a15",
110 "transparency_log_leaf_index": 41
107111}
108112```
109113
from line 143
139143 "resource_details": { "type": "message", "id": "msg_0ExampleExampleExample" },
140144 "accessor_department": "Safeguards",
141145 "reason_code": "policy_violation_investigation",
142 "organization_uuid": "00000000-1111-2222-3333-444444444444"
146 "organization_uuid": "00000000-1111-2222-3333-444444444444",
147 "transparency_log_leaf_index": 57
143148}
144149```
145150
from line 186
181186
182187### Notification timing
183188
184`anthropic_access` and `cmek_preserve` events are delivered to your Compliance API feed within two business days of the access or preservation they record. This feed should not be treated as a real-time alerting channel, and the `accessed_at` timestamp reflects when the access occurred, which might be up to two business days before the activity becomes visible in your feed. The `created_at` field reflects the time that the event became visible.
189`anthropic_access` and `cmek_preserve` events are delivered to your Compliance API feed within two business days of the access or preservation they record. This feed should not be treated as a real-time alerting channel, and the `accessed_at` timestamp reflects when the access occurred, which might be up to two business days before the activity becomes visible in your feed. The `created_at` field reflects the time Anthropic recorded the event, and the event usually becomes visible in your feed shortly after that time. These events do not follow the Activity Feed's usual 1-minute [indexing lag](https://platform.claude.com/docs/en/manage-claude/compliance-integration-patterns#window-polling): an event can become visible up to two business days after its `created_at`. If you poll the feed by `created_at` window, overlap consecutive windows by at least two business days for `anthropic_access` and `cmek_preserve` events so that a late-indexed event is not dropped.
185190
186191### Automated processing does not generate access events
187192
from line 235
230235 They are independent. With CMEK, safety preservation outside your key emits a separate `cmek_preserve` event on the same feed. See [CMEK content preservation](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation) and [CMEK](https://platform.claude.com/docs/en/manage-claude/cmek).
231236 </Accordion>
232237
238 <Accordion title="How can I tell that my Access Transparency record has not been altered?">
239 Verify your organization's transparency log (beta): an append-only, signed record of your Access Transparency events, with inclusion and consistency proofs you check on your own infrastructure. See [Verify Access Transparency events with the transparency log](https://platform.claude.com/docs/en/manage-claude/access-transparency-log).
240 </Accordion>
241
233242 <Accordion title="How do I request Access Transparency?">
234243 Contact your Anthropic account representative.
235244 </Accordion>
from line 246
237246
238247## Related resources
239248
249* [Verify Access Transparency events with the transparency log (beta)](https://platform.claude.com/docs/en/manage-claude/access-transparency-log)
240250* [Compliance API overview](https://platform.claude.com/docs/en/manage-claude/compliance-api)
241251* [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed)
242252* [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention)
No line in this hunk matches that.