You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.300,
ImprovementsSection of the release
What
An administrator can require Claude Code to be signed in to one specific claude.ai organization, using the forceLoginOrgUUID setting. Claude Code then checks that your login belongs to that organization.
That check has been reorganised. When Claude Code already knows your organization's ID, it now uses that ID instead of fetching your profile a second time. The messages you see are unchanged, including "Please log in with a permitted organization: claude auth login".
Why
There are fewer profile lookups during the check. The same check can also now be applied to other kinds of credentials, meaning other ways of signing in.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up forceLoginOrgUUID, on Deploy with Enterprise Admin Console.* **Allow only your organization:** set [`forceLoginOrgUUID`](/docs/cowork/hipaa-setup#what-each-claude-desktop-key-does) to your Claude organization's ID. This ID isn't [`deploymentOrganizationUuid`](/docs/third-party/claude-desktop/confi…third-party/claude-desktop/admin-consolesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up forceLoginOrgUUID, on Deploy with Enterprise Admin Console.
Anthropic's release notes agreeFixed a login refused by forceLoginOrgUUID leaving the refused organization's token stored, or live after /login
