{"version":"2.1.307","anchor":"org-pin-check-accepts-a-desktop-app-provided-sign-in","canonical_anchor":"org-pin-check-accepts-a-desktop-app-provided-sign-in","heading":"Organization sign-in rules now cover sign-ins from the desktop app","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/org-pin-check-accepts-a-desktop-app-provided-sign-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Organization sign-in rules now cover sign-ins from the desktop app\n\nWhen `forceLoginOrgUUID` pins an organization, Claude Code now also checks a sign-in provided by the desktop app\n\n**What**\n\nAdministrators can use the managed setting `forceLoginOrgUUID` to require that Claude Code is signed in to a particular organization. Before, Claude Code checked only the `CLAUDE_CODE_OAUTH_TOKEN` environment variable or stored credentials against it.\n\nIt now also checks a sign-in handed over by the desktop app. If that sign-in belongs to a different organization, Claude Code shows a message naming the desktop app and asking you to sign in to the desktop app with a permitted organization. Looking up which organization a sign-in belongs to may also reuse an earlier answer rather than asking the server again.\n\n**Why**\n\nOrganization pinning now also applies to Claude Code sessions started from the desktop app, so they cannot use an account from another organization.\n\n- Area: Managed Settings\n- Names: `forceLoginOrgUUID`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}