{"version":"2.1.269","anchor":"artifact-permission-checks-gained-cowritten-and-pageforei","canonical_anchor":"artifact-permission-checks-gained-cowritten-and-pageforei","heading":"Artifact permission checks gained 'cowritten' and 'pageForeign' co-authorship signals","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-permission-checks-gained-cowritten-and-pageforei","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact permission checks gained 'cowritten' and 'pageForeign' co-authorship signals\n\nArtifact permission checks now detect co-authorship and flag artifacts as foreign-owned on pages\n\n**Unclear.** The finding doesn't say how `pageForeign` or the co-authorship signals are used in the interface.\n\n**What**\n\nWhen resolving permissions or state for an artifact, Claude Code now checks whether the artifact was co-written or authored by someone other than the current user, based on signals like whether the artifact is marked as co-written, its artifact kind, and whether the current user's role is something other than owner. A new `pageForeign` flag is now included in the results to indicate this.\n\n**Why**\n\nThis lets the interface distinguish artifacts a user owns from ones they merely collaborate on or don't own, which can affect what permissions or actions are appropriate to show.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}