{"version":"2.1.309","anchor":"artifact-create-notice-from-org-config","canonical_anchor":"artifact-create-notice-from-org-config","heading":"New organisation setting: artifact_create_notice","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/artifact-create-notice-from-org-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### New organisation setting: artifact_create_notice\n\nOrganisations can set an artifact_create_notice, defaulting to a message that a person must approve each new artifact\n\n**Unclear.** Where and when this notice is shown is not stated.\n\n**What**\n\nA new organisation-level setting, `artifact_create_notice`, carries a text notice about creating artifacts. Its default text is \"Your organization requires a person to approve each new artifact.\"\n\n- It arrives through the remote configuration your organisation sets.\n\n- In managed settings (settings an administrator controls), the logic that treats a configuration as simple now also returns false when `artifact_create_notice` is set. It already did this for `monitoring_notice` and `defaults`.\n\n**Why**\n\nIf your organisation sets this field, Claude Code no longer treats your managed settings as a simple configuration, and the notice text is available to show around artifact creation.\n\n- Area: Managed Settings\n- Names: `artifact_create_notice`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}