forceLoginOrgUUID
A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.138 and was gone by v2.1.284.
Pin claude.ai logins to your organization; only a managed source enforces it
Anthropic's own wording. Read off All settings, captured 2026-10-22.
In the changelogs
14Releases whose published page names forceLoginOrgUUID.
-
v2.1.307
Organization sign-in rules now cover sign-ins from the desktop app
When
forceLoginOrgUUIDpins an organization, Claude Code now also checks a sign-in provided by the desktop appnamed in this entry, found in this entry's text
-
v2.1.300
Login now checks your organisation before saving new credentials
Signing in now checks the new token against the organisation required by managed settings before saving it, and fails if it does not match
found in this entry's text, named in this entry
-
v2.1.300
Organization login check fetches your profile less often
The check that you signed in to your required organization now reuses an organization ID already fetched instead of fetching your profile again
found in this entry's text, named in this entry
-
v2.1.299
Machine policy can now be checked for a pinned sign-in organisation
Claude Code can now read the machine's admin policy to see whether it pins sign-in to an organisation with
forceLoginOrgUUIDfound in this entry's text
-
v2.1.299
Locally managed login restrictions now take priority over server-managed settings
forceLoginOrgUUID and forceLoginMethod set through MDM or a managed file now apply ahead of server-managed settings
found in this entry's text
-
v2.1.299
The saved copy of managed settings is checked before it is used
Claude Code now ignores its saved copy of organization-managed settings unless it matches the account and organization it is pinned to
found in this entry's text, named in this entry
-
v2.1.290
Claude Code can detect an existing sign-in from token variables
A new check finds out whether a usable sign-in already exists, for example from
CLAUDE_CODE_OAUTH_TOKENfound in this entry's text
-
v2.1.284
Clearer error when a managed login policy clashes with your API key or token
When managed settings require a specific sign-in but another credential is set, the error names that credential, where it came from, and how to fix it
found in this entry's text, named in this entry
-
v2.1.281
Managed config: forceLoginOrgUUID validation, new disableMultiAccount, microsoftAuthBroker 'required'
Managed settings now check that
forceLoginOrgUUIDis a UUID or a list of UUIDs, and adddisableMultiAccountand arequiredvalue formicrosoftAuthBrokerfound in this entry's text, named in this entry
-
v2.1.268
New managed-settings key gatewayInternalNetworks joins highest-source-wins auth pins
New managed setting gatewayInternalNetworks joins the group taken only from the top-priority settings source
found in this entry's text
-
v2.1.268
gatewayInternalNetworks added to managed-settings merge exception list
gatewayInternalNetworks added to the list of managed-settings fields that replace rather than merge
found in this entry's text
-
v2.1.257
managedSettings 'merge' mode composition rules made explicit and expanded
Managed settings merge mode now documents which fields the helper replaces wholesale rather than merging.
found in this entry's text
-
v2.1.242
Managed settings can now merge across sources instead of the top one winning
Admins can set managedSourcesBehavior to merge managed settings sources instead of only the top one.
found in this entry's text
-
v2.1.223
Managed-settings tier merge no longer falls through for two keys
Two admin-managed settings now come only from the top policy tier, so lower tiers can't sneak values in.
named in this entry, found in this entry's text
First cited
4The earliest release whose published evidence quoted forceLoginOrgUUID was v2.1.223, 5 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
2Build by build
149One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.