access-transparency changedmanage-claude/access-transparency
Recorded here
Lines+1added
Lines−0removed
From line
94
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
The whole hunk
from line 94, old and new numbered
/
from line 94
9494| `workspace_id` | string or null | The workspace the content belongs to |
9595| `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 |
9696| `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) |
97| `user_profile_id` | string | The [user profile](https://platform.claude.com/docs/en/manage-claude/user-profiles) the accessed or preserved content was created under. Tagged ID format (`uprof_...`). Present only when the content was created under a user profile |
9798
9899Example JSON message:
99100
No line in this hunk matches that.