{"version":"2.1.280","anchor":"managed-settings-disable-reason-for-workflows-now-covers-ena","canonical_anchor":"managed-settings-disable-reason-for-workflows-now-covers-ena","heading":"Managed-settings disable reason for workflows now covers enableWorkflows: false","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/managed-settings-disable-reason-for-workflows-now-covers-ena","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Managed-settings disable reason for workflows now covers enableWorkflows: false\n\nWorkflows can now also be disabled via 'enableWorkflows: false' set above your own settings\n\n**What**\n\nDynamic workflows (Claude Code's feature for running multi-step orchestrations) can be turned off in several ways. The documented list of causes now explicitly includes `enableWorkflows: false` being set by a settings layer above your own (such as an organization or managed policy), in addition to the existing `disableWorkflows` setting and the `CLAUDE_CODE_DISABLE_WORKFLOWS` environment variable.\n\n**Why**\n\nThis clarifies that an admin-level `enableWorkflows: false` is now a recognized, explained reason workflows might be unavailable to you, rather than appearing unexplained.\n\n- Area: Elsewhere\n- Names: `enableWorkflows`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}