{"version":"2.1.275","anchor":"new-cross-organization-restriction-on-copying-artifact-files","canonical_anchor":"new-cross-organization-restriction-on-copying-artifact-files","heading":"New cross-organization restriction on copying artifact files during publish","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-cross-organization-restriction-on-copying-artifact-files","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New cross-organization restriction on copying artifact files during publish\n\nPublishing an artifact now blocks copying files from another organization's artifact unless ownership is confirmed\n\n**What**\n\nWhen publishing an artifact that copies files from another artifact via a `files` map, Claude Code now checks whether the source artifact belongs to a different organization. If it does and that ownership can't be confirmed, the whole publish is rejected with a new error. Separately, publishing is now explicitly denied outright when the destination artifact itself belongs to a different organization.\n\n**Why**\n\nThis closes off a way that content could be copied across organization boundaries without proper ownership checks, protecting artifacts from being published into or sourced from an organization that shouldn't have access to them.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}