compliance-org-data changedmanage-claude/compliance-org-data
Nearest release: v2.1.309, published 13 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+30added
Lines−19removed
From line
29
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
The whole hunk
from line 29, old and new numbered
/
from line 29
2929 -H "anthropic-version: 2023-06-01"
3030```
3131
32```text Response wrap
32```json Response
3333{
3434 "data": [
3535 {
from line 80
8080 --data-urlencode "limit=500"
8181```
8282
83```text Response wrap
83```json Response
8484{
8585 "data": [
8686 {
87 "id": "user_01XyDMpzjS89pFZXqSFUBDr6",
87 "id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
8888 "full_name": "Priya Sharma",
9090 "organization_role": "admin",
from line 96
9696}
9797```
9898
99The user IDs returned here are the same `user_...` identifiers accepted by the [Query the Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) `actor_ids[]` filter and the `user_ids[]` filters on [Retrieve chats and messages](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-chats-and-messages) and the [remote session list](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-remote-sessions); the [local session list](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions) has no user filter, so attribute local sessions by the `user.id` on each session object. The `organization_role` field carries the user's built-in membership level within the listed organization (one of `admin`, `billing`, `claude_code_user`, `developer`, `managed`, `membership_admin`, `owner`, `primary_owner`, or `user`), an axis independent of any custom RBAC role assignments returned by [List roles](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-roles). A typical eDiscovery flow lists users for one or more organizations, filters against your own external records, and feeds the resulting IDs into chat and project queries.
99The user IDs returned here are the same `user_...` identifiers accepted by the [Query the Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) `actor_ids[]` filter. The `user_ids[]` filters on [Retrieve chats and messages](https://platform.claude.com/docs/en/manage-claude/compliance-content-data#retrieve-chats-and-messages) and the [remote session list](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-remote-sessions) accept the same identifiers. The [local session list](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retrieve-local-sessions) has no user filter, so attribute local sessions by the `user.id` on each session object. The `organization_role` field carries the user's built-in membership level within the listed organization (one of `admin`, `billing`, `claude_code_user`, `developer`, `managed`, `membership_admin`, `owner`, `primary_owner`, or `user`), an axis independent of any custom RBAC role assignments returned by [List roles](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-roles). A typical eDiscovery flow lists users for one or more organizations, filters against your own external records, and feeds the resulting IDs into chat and project queries.
100100
101101A user only appears here while they are an active member of the organization. Removed users are dropped from the list immediately. Their historical activity remains queryable through the Activity Feed for the full retention window, indexed by the same `user_...` ID.
102102
from line 115
115115 -H "anthropic-version: 2023-06-01"
116116```
117117
118```text Response wrap
118```json Response
119119{
120120 "data": [
121121 {
122122 "user": {
123 "id": "user_01XyDMpzjS89pFZXqSFUBDr6",
123 "id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
125125 },
126126 "conversation_preferences": "Keep answers brief and cite sources.",
from line 145
145145 -H "anthropic-version: 2023-06-01"
146146```
147147
148```text Response
148```json Response
149149{
150150 "data": [
151151 {
from line 180
180180 -H "anthropic-version: 2023-06-01"
181181```
182182
183```text Response wrap
183```json Response
184184{
185185 "data": [
186186 {
from line 207
207207 -H "anthropic-version: 2023-06-01"
208208```
209209
210```text Response wrap
210```json Response
211211{
212212 "data": [
213213 {
214 "user_id": "user_01XyDMpzjS89pFZXqSFUBDr6",
214 "user_id": "user_01WxYzAbCdEfGhJkMnPqRsTu",
216216 "created_at": "2025-06-01T10:00:00Z",
217217 "updated_at": "2025-06-15T14:30:00Z"
from line 228
228228
229229The [Get effective organization settings](https://platform.claude.com/docs/en/api/compliance/organizations/settings/retrieve) endpoint returns the settings in force for one organization under your parent: the enforced state after regulatory restrictions (such as HIPAA), feature-availability rules, organization-type defaults, and inter-feature dependencies are applied, which can differ from what an administrator configured. Use it to attest that retention windows, content redaction, single sign-on enforcement, the IP allowlist, and session-duration controls match your documented baseline, without administrator Console access.
230230
231This endpoint requires `read:compliance_org_data`; a key without that scope returns [403 Forbidden](https://platform.claude.com/docs/en/manage-claude/compliance-errors#403-forbidden). The target must be one of the parent's linked organizations: the parent organization itself is not a valid target. An unknown organization, an organization ID that is not a valid UUID, an organization outside your parent's tree, and a parent organization that does not yet have access to this endpoint all return the same [404 Not Found](https://platform.claude.com/docs/en/manage-claude/compliance-errors#404-not-found), so a 404 does not reveal whether an organization exists. The settings endpoint is enabled per parent organization separately from the rest of the Compliance API; if every request returns 404, contact your Anthropic representative.
231This endpoint requires `read:compliance_org_data`; a key without that scope returns [403 Forbidden](https://platform.claude.com/docs/en/manage-claude/compliance-errors#403-forbidden). The target must be one of the parent's linked organizations: the parent organization itself is not a valid target. All of the following return the same [404 Not Found](https://platform.claude.com/docs/en/manage-claude/compliance-errors#404-not-found):
232232
233* An unknown organization
234* An organization ID that is not a valid UUID
235* An organization outside your parent's tree
236* A parent organization that does not yet have access to this endpoint
237
238A 404 therefore does not reveal whether an organization exists. The settings endpoint is enabled per parent organization separately from the rest of the Compliance API; if every request returns 404, contact your Anthropic representative.
239
233240<Note>
234241 Before June 30, 2026, this endpoint required the separate `read:compliance_org_settings` scope. That scope has been retired: it can no longer be selected or granted when creating a key, and a key that carries only the retired scope returns [403 Forbidden](https://platform.claude.com/docs/en/manage-claude/compliance-errors#403-forbidden). Create a new Compliance Access Key with `read:compliance_org_data` instead.
235242</Note>
from line 250
243250
244251The response is a list of typed setting rows, and which rows appear varies by organization: a setting the organization's administrators cannot change, because it is controlled by Anthropic policy or not available to the organization, is omitted from the list. Treat a missing row as "not controllable by this organization's administrators", not as "off". The following abridged example shows three of the rows a response can contain:
245252
246```text Response wrap
253```json Response
247254{
248255 "type": "effective_organization_settings",
249256 "organization_id": "91012d09-e48b-438e-a489-1bebfd8fa6f9",
from line 298
291298
292299The top-level `organization_id` is the organization's bare UUID: the same value as `uuid` in the organizations list, not the `org_`-prefixed form that `organization_id` carries on Activity Feed, chat, and project records (see the [organization identifier table](https://platform.claude.com/docs/en/manage-claude/compliance-org-data#list-organizations)).
293300
294Rows reflect the enforced state rather than the last-stored configuration: for example, `sso_provisioning_mode` reports a configured SCIM mode only while directory sync is enabled, `ip_allowlist_enabled` is `true` only while the allowlist is on and has at least one active range, and `code_execution_network_egress_enabled` is `false` whenever code execution is off.
301Rows reflect the enforced state rather than the last-stored configuration, as in these examples:
302
303* `sso_provisioning_mode` reports a configured SCIM mode only while directory sync is enabled.
304* `ip_allowlist_enabled` is `true` only while the allowlist is on and has at least one active range.
305* `code_execution_network_egress_enabled` is `false` whenever code execution is off.
295306
296307The response reflects the state at read time; nothing is snapshotted. Changes to most of these settings surface as events in the [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed); use this endpoint for the current resolved state and the feed to audit who changed what, and when.
297308
No line in this hunk matches that.