{"version":"2.1.307","anchor":"managed-settings-fetch-failure-message-mentions-stale-restri","canonical_anchor":"managed-settings-fetch-failure-message-mentions-stale-restri","heading":"Managed settings errors now say when older restrictions still apply","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/managed-settings-fetch-failure-message-mentions-stale-restri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Managed settings errors now say when older restrictions still apply\n\nWhen fetching managed settings fails but saved restrictions still apply, Claude Code now says so and tells you to run `claude auth logout` to clear them\n\n**What**\n\nManaged settings are rules an organisation applies to Claude Code. When Claude Code cannot fetch them, the message used to say that no policy was applied. When a saved, older copy of the restrictions still applies, the message now says so. It also tells you that running `claude auth logout` will clear them, and that this signs you out of all accounts.\n\n**Why**\n\nYou can now see why restrictions are still in force after a failed fetch, and how to remove them.\n\n- Area: Managed Settings\n- Names: `claude auth logout`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}