{"version":"2.1.285","anchor":"compliance-status-label-and-notification-reworded","canonical_anchor":"compliance-status-label-and-notification-reworded","heading":"The Compliance row in \/status is now called Organization configuration","tier":"notice","area":"Terminal UI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/compliance-status-label-and-notification-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### The Compliance row in \/status is now called Organization configuration\n\nIn \/status, the Compliance row is now called Organization configuration, and the related notice is shorter and appears once\n\n**Unclear.** It is not clear what triggers the notice.\n\n**What**\n\nIn `\/status`, the row that was labelled \"Compliance\" is now labelled \"Organization configuration\". The notice shown when organization policy restricts Claude Code has changed too:\n\n- It no longer says \"some features are restricted\" and now ends with \" \u00b7 \/status\".\n\n- It is one shared notice, not a separate one for each restriction.\n\n- It is checked once at startup against the current state.\n\n**Why**\n\nIf you work under an organization policy, you will see different wording in `\/status` and in this notice.\n\n- Area: Terminal UI\n- Names: `\/status`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}