{"version":"2.1.285","anchor":"managed-policy-read-failure-message","canonical_anchor":"managed-policy-read-failure-message","heading":"Clear error when managed policy settings cannot be read","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/managed-policy-read-failure-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Clear error when managed policy settings cannot be read\n\nClaude Code has a new error saying it could not read managed policy settings, which may restrict allowed API providers\n\n**Unclear.** It is not clear what triggers this error or how it relates to a related remotely controlled setting.\n\n**What**\n\nManaged policy settings are settings an administrator sets for every Claude Code user in an organization. Claude Code now has an error for when it cannot read them. The error says this may restrict which API providers the machine may use, which is controlled by the `allowedProviders` setting, and tells you to contact your administrator.\n\n**Why**\n\nA failure to read your organization's policy is now reported to you, which helps explain why an API provider might be blocked.\n\n- Flag `tengu_org_policy_denied`: Not enough to say (read for one account on one subscription tier against v2.1.285; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Managed Settings\n- Names: `allowedProviders`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}