{"version":"2.1.282","anchor":"artifacts-with-an-unproven-org-relation-now-treated-as-off-o","canonical_anchor":"artifacts-with-an-unproven-org-relation-now-treated-as-off-o","heading":"Artifacts not proven to come from your organization are treated as external","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/artifacts-with-an-unproven-org-relation-now-treated-as-off-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Artifacts not proven to come from your organization are treated as external\n\nPublished artifacts whose link to your organization can't be confirmed now get the same restricted handling as external or public ones\n\n**Unclear.** It is not clear whether the artifacts feature itself is switched on for all users.\n\n**What**\n\nClaude Code now sorts published artifacts (pages that Claude or others have published) into one of five relations to you: external, public, your own, from the same organization, or unproven. Only artifacts that are your own or from the same organization get the normal treatment.\n\nAnything else, including artifacts whose relation cannot be proven, is now handled the way external or public artifacts already were:\n\n- Its audience is not classified as a channel or shared audience\n\n- Excerpts of its page content are not copied inline into what Claude reads\n\n**Why**\n\nWhen Claude Code cannot confirm that an artifact belongs to your organization, it now assumes it does not. This errs on the safe side and keeps content from unknown sources out of the conversation.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}