{"version":"2.1.275","anchor":"artifact-write-consent-now-distinguishes-edit-access-by-anot","canonical_anchor":"artifact-write-consent-now-distinguishes-edit-access-by-anot","heading":"Artifact write consent now distinguishes edit-access-by-another-org from ownership","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-write-consent-now-distinguishes-edit-access-by-anot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact write consent now distinguishes edit-access-by-another-org from ownership\n\nArtifact write permissions now separate editor access granted by another org from actual ownership\n\n**Unclear.** The finding does not say what the different treatment actually looks like for the user.\n\n**What**\n\nArtifact permission logic gains two new fields, `invitedByOtherOrg` and `canWrite`, computed by probing the artifact's role and mode. These feed directly into the write-consent decision, so Claude Code can now tell apart an artifact you own from one where someone in a different organization gave you editor access.\n\n**Why**\n\nThis lets Claude Code apply different consent handling when writing to an artifact you don't fully own but were invited to edit by another org, rather than treating all editable artifacts the same way.\n\n- Area: Artifacts\n- Names: `invitedByOtherOrg`, `canWrite`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}