{"version":"2.1.281","anchor":"design-and-slides-artifact-commands-each-get-their-own-org-p","canonical_anchor":"design-and-slides-artifact-commands-each-get-their-own-org-p","heading":"Design and Slides artifact commands each get their own org policy key","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/design-and-slides-artifact-commands-each-get-their-own-org-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Design and Slides artifact commands each get their own org policy key\n\nThe Design and Slides artifact commands can now each be allowed or blocked separately by organisation policy\n\n**What**\n\nThe Design and Slides artifact commands each now have their own organisation policy key, a named setting that an organisation's administrators control from the server:\n\n- Design: `allow_cobalt_plinth_bramble`\n\n- Slides: `allow_cobalt_plinth_juniper`\n\nEach command is available only if its key allows it, on top of the conditions that already applied. When no policy has been stored locally yet, the key counts as allowed unless it is known to be denied. The real answer comes from the organisation's policy on the server.\n\n**Why**\n\nAn organisation can now switch Design and Slides on or off one at a time instead of only together. If one of these commands is missing for you, your organisation's policy may be the reason."}