{"version":"2.1.307","anchor":"organization-added-as-a-recognised-scope-value","canonical_anchor":"organization-added-as-a-recognised-scope-value","heading":"\"organization\" is accepted as a scope value","tier":"internal","area":"Organizations","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/organization-added-as-a-recognised-scope-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### \"organization\" is accepted as a scope value\n\nClaude Code now accepts \"organization\" as a scope value, alongside service, channel and group_pool\n\n**Unclear.** It is not clear what an \"organization\" scope applies to.\n\n**What**\n\nClaude Code reads a scope from a metadata value. It now accepts \"organization\" there. Before, it accepted only service, channel and group_pool.\n\n**Why**\n\nThis points toward settings or limits that can apply to a whole organization.\n\n- Area: Organizations\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}