{"version":"2.1.317","anchor":"remote-managed-settings-desktop-notice-and-stored-login-ref","canonical_anchor":"remote-managed-settings-desktop-notice-and-stored-login-ref","heading":"Desktop notice for remotely managed settings, and a reason when a saved login is held back","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/remote-managed-settings-desktop-notice-and-stored-login-ref","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Desktop notice for remotely managed settings, and a reason when a saved login is held back\n\nClaude Code adds a name for a desktop notice about remotely managed settings, and errors that hold back a saved login now keep a reason\n\n**Unclear.** It is not clear whether or when a desktop notice about remotely managed settings is actually shown to users.\n\n**What**\n\nTwo small additions concern login and settings:\n\n- Remotely managed settings: Claude Code now has a name for a desktop notice about these settings. Remotely managed settings are settings an organisation sets centrally, not on your own machine.\n\n- Saved logins: when Claude Code refuses to use a login it has stored, the error it raises now keeps a reason for the refusal.\n\n**Why**\n\nBoth are small additions around how managed settings and saved logins are handled.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}