{"version":"2.1.304","anchor":"managed-folder-check-as-a-new-reason-for-refreshing-settings","canonical_anchor":"managed-folder-check-as-a-new-reason-for-refreshing-settings","heading":"Settings reload messages can now blame a check of this machine's managed folder","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/managed-folder-check-as-a-new-reason-for-refreshing-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Settings reload messages can now blame a check of this machine's managed folder\n\nWhen settings reload after a check of the machine's managed settings folder, Claude Code now says so instead of blaming an organization policy change\n\n**What**\n\nManaged settings are settings an organization or administrator puts in place on a machine. Claude Code watches for changes to them and reloads settings when they change.\n\nThere is now a second reason it can give for a reload. When the managed folder on this machine changed but the other managed-settings value it watches did not, the reload is described as happening \"after a check of this machine's managed folder\". Before, the only reason given was \"after the organization's managed settings changed\".\n\n**Why**\n\nReload messages now point to a local check of the managed folder when that is what caused the change, rather than suggesting your organization changed its policy.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}