{"version":"2.1.314","anchor":"managed-settings-consent-skipped-silently-for-first-party-tr","canonical_anchor":"managed-settings-consent-skipped-silently-for-first-party-tr","heading":"Organisation-signed managed settings can skip the approval prompt","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/managed-settings-consent-skipped-silently-for-first-party-tr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Organisation-signed managed settings can skip the approval prompt\n\nManaged settings that pass a signature and organisation check can now apply without the security approval prompt\n\n**What**\n\nManaged settings are settings an organisation sends to Claude Code from its servers. When they include settings that could be risky, Claude Code shows a security prompt asking you to approve them. Before, that prompt appeared whenever the risky-settings check applied, unless no check was needed.\n\nClaude Code can now skip the prompt silently when both of these are true:\n\n- You are signed in with your account through OAuth, the standard sign-in method, and your organisation matches.\n\n- The settings arrive signed, and a check confirms both the signature and that they belong to your organisation.\n\nClaude Code reports whether the source was trusted. Settings you approve and settings that need no check are handled as before.\n\n**Why**\n\nIf your organisation's settings pass this check, you may no longer see the approval prompt for managed settings.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}