compliance-integration-patterns changedmanage-claude/compliance-integration-patterns
Nearest release: v2.1.239, 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+10added
Lines−7removed
From line
94
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 94, old and new numbered
/
from line 94
9494
9595Each `Activity` carries fields you can join against events already in your SIEM (Splunk, Datadog, Microsoft Sentinel, Cribl, or similar):
9696
97| Compliance API field | Join target |
98| --------------------- | ----------------------------------------------- |
99| `actor.user_id` | Your identity provider's stable user identifier |
100| `actor.email_address` | Directory email when a stable ID is unavailable |
101| `actor.ip_address` | Network, VPN, and endpoint logs |
102| `created_at` | Time-window correlation across any source |
97| Compliance API field | Join target |
98| --------------------- | ----------------------------------------------------------------------- |
99| `actor.user_id` | Your identity provider's stable user identifier |
100| `actor.email_address` | Directory email when a stable ID is unavailable |
101| `actor.ip_address` | Network, VPN, and endpoint logs |
102| `actor.user_agent` | Endpoint and device inventory, and the client app that made the request |
103| `created_at` | Time-window correlation across any source |
103104
104`actor.user_id` and `actor.email_address` are present when `actor.type` is `user_actor`; check the discriminator before reading them. `user_id` is a stable, opaque identifier for the user account: it is consistent across every Compliance API endpoint and activity payload, and it does not change when the user's email or display name changes. Use `user_id`, not `email_address`, as the primary join key.
105`actor.user_id` and `actor.email_address` are present when `actor.type` is `user_actor`. `actor.ip_address` and `actor.user_agent` are absent on some actor types, such as `anthropic_actor` and `scim_directory_sync_actor`. Check the discriminator before reading any of these fields. `user_id` is a stable, opaque identifier for the user account: it is consistent across every Compliance API endpoint and activity payload, and it does not change when the user's email or display name changes. Use `user_id`, not `email_address`, as the primary join key.
105106
106107Calls to the Compliance API itself emit `compliance_api_accessed` activities. Ingest these alongside other activity types so your SIEM records who queried compliance data, and when. Pass `activity_types[]=compliance_api_accessed` to scope the query, then in your client, read `actor.api_key_id` from each activity whose `actor.type` is `api_actor` to attribute the access to a specific Compliance Access Key or Admin API key.
107108
from line 137
136137* The starting cursor and the terminal `last_id`.
137138* The number of records exported.
138139* The run timestamp and the `request-id` of the final page.
140
141Activity volume is not a completeness check. The `claude_*_viewed` activity types, such as `claude_chat_viewed`, follow each app's loading pattern (see [Understand the Activity object](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed#understand-the-activity-object)). A period with chat messages but no `claude_chat_viewed` activities does not on its own indicate missing data. Rely on the traversal and the overlap or reconciliation pass described in [Window polling](https://platform.claude.com/docs/en/manage-claude/compliance-integration-patterns#window-polling) instead.
139142
140143The content endpoints (chats, files, projects, project attachments, and local and remote session transcripts) serve Claude Enterprise data only. The Activity Feed surfaces administrative and resource events organization-wide. The Compliance API does not include:
141144
No line in this hunk matches that.