{"version":"2.1.281","anchor":"managed-locks-marked-reasonshipsoffbox-are-reported-as-refus","canonical_anchor":"managed-locks-marked-reasonshipsoffbox-are-reported-as-refus","heading":"Managed locks marked reasonShipsOffBox are reported as refusals","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-locks-marked-reasonshipsoffbox-are-reported-as-refus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed locks marked reasonShipsOffBox are reported as refusals\n\nSaving a setting blocked by a managed lock marked reasonShipsOffBox now reports a refusal, not \"locked\"\n\n**Unclear.** The finding does not say what `reasonShipsOffBox` means or how a refusal looks different to you from a lock.\n\n**What**\n\nA managed lock is a restriction set by whoever administers your Claude Code setup, such as your organisation, that stops a setting from being changed. When you try to save a setting under a lock marked `reasonShipsOffBox`, the result now comes back as kind \"refusal\". Before, it came back as \"locked\".\n\n**Why**\n\nThese blocked saves are now reported in a different category from ordinary managed locks."}