{"version":"2.1.309","anchor":"org-required-approval-for-creating-artifacts","canonical_anchor":"org-required-approval-for-creating-artifacts","heading":"Artifact creation is refused when your organization needs approval and no one can give it","tier":"notice","area":"Artifacts","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/org-required-approval-for-creating-artifacts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Artifact creation is refused when your organization needs approval and no one can give it\n\nIf your organization needs a person to approve each new artifact, Claude Code refuses to create one when no one can be asked\n\n**What**\n\nSome organizations require a person to approve each new artifact. Under that rule, Claude Code now refuses to create an artifact when there is nobody to ask. That covers these cases:\n\n- permission prompts are turned off or bypassed\n\n- a schedule started the turn\n\n- a message from outside Claude Code started the turn\n\n**Why**\n\nIf your organization has this rule, unattended or scheduled sessions can no longer create artifacts.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}