{"version":"2.1.300","anchor":"cowork-cloud-holds-on-managed-policy-settings","canonical_anchor":"cowork-cloud-holds-on-managed-policy-settings","heading":"Cowork cloud keeps strict managed policy settings once they are set","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/cowork-cloud-holds-on-managed-policy-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Cowork cloud keeps strict managed policy settings once they are set\n\nIn Cowork cloud, once certain managed policy settings are tightened, a later settings update can no longer loosen them\n\n**What**\n\nIn Cowork cloud, Claude Code now holds on to certain managed policy settings once they have been applied. A later settings update cannot loosen them. The held settings are:\n\n- `allowManagedHooksOnly`, which runs only the hooks your organization deploys\n\n- `disableAllHooks`, which turns off hooks, a custom status line and a custom `@` file suggestion command\n\n- `disableCommandPluginSources`, which blocks plugins that install by running a command\n\n- `allowManagedModsOnly`, a plugin option\n\nThe held values are combined back in with the incoming settings, with `managedSourcesBehavior` set to merge.\n\n**Why**\n\nOnce an organization tightens one of these policies in Cowork cloud, a later refresh of the settings cannot quietly undo it.\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"}