Observed source change · Anthropic
Claude release notes documentation changed
Published documentation; runtime behavior and legal interpretation not established.
Last unchanged check: 2026-10-21T20:55:13Z
First changed check: 2026-10-21T23:00:13Z
Before
- We've added the `enforcement_status` and `enforcement_actions` fields to [user profiles](https://platform.claude.com/docs/en/manage-claude/user-profiles), so you can see whether Anthropic has restricted or banned one of your end customers. To find the profiles that have an open restriction or ban, [list your profiles](https://platform.claude.com/docs/en/api/user_profiles/list) with the new `enforcement_status[]` filter. See [Check whether Anthropic has restricted or banned a profile](https://platform.claude.com/docs/en/manage-claude/user-profiles#check-whether-anthropic-has-restricted-or-banned-a-profile). * In Claude Managed Agents, the [`web_search` tool](https://platform.claude.com/docs/en/managed-agents/tools#available-tools) now follows your organization's web search domain restrictions set in the Claude Console. The agent receives only the search results that both the organization's domain restrictions and …
After
* We've added the `enforcement_status` and `enforcement_actions` fields to [user profiles](https://platform.claude.com/docs/en/manage-claude/user-profiles), so you can see whether Anthropic has restricted or banned one of your end customers. To find the profiles that have an open restriction or ban, [list your profiles](https://platform.claude.com/docs/en/api/user_profiles/list) with the new `enforcement_status[]` filter. See [Check whether Anthropic has restricted or banned a profile](https://platform.claude.com/docs/en/manage-claude/user-profiles#check-whether-anthropic-has-restricted-or-banned-a-profile). * Organization admins can now turn off web fetch for their organization on the [**Capabilities**](https://platform.claude.com/settings/capabilities) page of the Claude Console. With web fetch off, a Messages API request that includes the web fetch tool fails …
Capture provenance and limitations
Raw before SHA-256: e44246a59866b69fb396bb5d53fa47fd4601791d0f388131423b76c407ac132b
Raw after SHA-256: 632020f4b3f31e65f9e9aa4b3a0a32d19a9bed30be6104247f0251f8753aafde
Full source responses are retained in the private evidence archive. Public excerpts show changed wording and may be truncated. The observed interval does not establish the vendor’s exact edit time. Hashes identify retained bytes; they are not an independent timestamp certificate.
Download archived excerpts and capture metadata · Back to the tracker