{"version":"2.1.285","anchor":"org-policy-can-refuse-with-provider-not-allowed","canonical_anchor":"org-policy-can-refuse-with-provider-not-allowed","heading":"Organization policy refusals now say when a provider is not allowed","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/org-policy-can-refuse-with-provider-not-allowed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Organization policy refusals now say when a provider is not allowed\n\nWhen your organization's policy blocks something because the provider is not allowed, the refusal now says so instead of using the general reason\n\n**Unclear.** It is not clear which command shows this refusal.\n\n**What**\n\nWhen a policy set by your organization refuses something, the refusal now carries the reason `provider_not_allowed` when the provider is not permitted. A provider is the service Claude Code reaches Claude through. Before, every such refusal was marked with the same reason, `org_pin`.\n\n**Why**\n\nIt is now possible to tell apart a refusal because the provider is not allowed from other policy refusals.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}