{"version":"2.1.275","anchor":"artifact-read-responses-now-carry-a-share-menu-payload-for-o","canonical_anchor":"artifact-read-responses-now-carry-a-share-menu-payload-for-o","heading":"Artifact reads now include Share menu access details","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-read-responses-now-carry-a-share-menu-payload-for-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact reads now include Share menu access details\n\nReading an artifact you own now returns who can access it via the Share menu, including external sharing and invite status\n\n**What**\n\n- When reading an artifact as its owner, the response can now include a `shareMenu` object listing which read access modes are assignable, plus optional `externalSharing` and `externalInvites` flags, derived from permission data.\n\n- For owner-role artifacts that aren't type-locked and have a share menu, Claude Code now appends a descriptive text summary to the artifact's audience description, phrased like \"(from the page's Share menu the user's plan and organization allow: ...)\", noting whether a public link is unavailable and whether external email invites are turned on or off.\n\n**Why**\n\nThis surfaces sharing and access permissions directly when reading an artifact, so it's clear who can see or be invited to it without checking the Share menu separately.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}