{"version":"2.1.304","anchor":"managed-settings-lostsigninpins-and-richer-held-settings-re","canonical_anchor":"managed-settings-lostsigninpins-and-richer-held-settings-re","heading":"Cloud sessions report more about managed settings that were not applied","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/managed-settings-lostsigninpins-and-richer-held-settings-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Cloud sessions report more about managed settings that were not applied\n\nFor cloud sessions under managed settings, Claude Code now tracks lost sign-in settings and reports more about which settings were held back\n\n**What**\n\nManaged settings are settings an organization sets for its users. For cloud sessions, which run on remote machines rather than your own computer, Claude Code now keeps track of more when it merges these settings:\n\n- Sign-in settings that were meant to be fixed in place but were lost\n\n- Settings that were not held, and content that was the only thing held\n\n- Allow lists that were held back, beyond the one for known plugin marketplaces that was reported before\n\nWhen a policy check fails, the error now also says whether the server gave an error code, whether the server refused the sign-in, and whether no response came back.\n\n**Why**\n\nCloud sessions under an organization's managed settings may behave more strictly as a result.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}