'%3e%3crect%20x='16'%20y='51'%20width='68'%20height='27'%20rx='13.5'/%3e%3ccircle%20cx='32'%20cy='53'%20r='15'/%3e%3ccircle%20cx='53'%20cy='43'%20r='20'/%3e%3ccircle%20cx='71'%20cy='57'%20r='12'/%3e%3c/g%3e%3c/svg%3e){kind=small}
Cloud Changelog
November 5, 2026 · Anthropic
Claude Console IP allowlist in beta, and Admin API endpoint to sign members out
- You can now set up an IP allowlist for your organization in the Claude Console, in beta. Requests to covered services from addresses not on your list are refused, which limits where a leaked API key can be used. Add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization. See IP allowlisting for what’s covered and how to set it up.
- You can now sign a member of your Claude Enterprise (claude.ai) organization out of Claude everywhere with the Admin API (see the Admin API reference).
POST /v1/organizations/users/{user_id}/sign_outis in beta, and every request must include theadmin-user-sign-out-2026-10-08beta header. It ends the member’s sign-in sessions and trusted devices on every browser and device, and their OAuth tokens for your organization. The member stays in the organization and can sign in again right away. See Sign a member out everywhere for the key scope that the request needs and for what it doesn’t end.