{"version":"2.1.275","anchor":"artifact-comment-threads-gain-an-outside-your-organization","canonical_anchor":"artifact-comment-threads-gain-an-outside-your-organization","heading":"Artifact comment threads gain an \"outside your organization\" access note and reply lockout","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-comment-threads-gain-an-outside-your-organization","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact comment threads gain an \"outside your organization\" access note and reply lockout\n\nArtifact comment threads now flag out-of-organization participants and block Claude from replying on their behalf\n\n**What**\n\nWhen Claude Code processes comment threads on an artifact or document, it now tracks a second set of accounts representing organization membership. When a commenter is marked as \"outside your organization,\" the access explanation now clarifies that this means the server recorded that person as invited from another organization. Additionally, when a thread is flagged this way, Claude is instructed not to reply to or resolve the thread directly; instead it must answer within the session and tell the user the answer can't be posted to the thread from there.\n\n**Why**\n\nThis prevents Claude from acting on comment threads involving people outside the organization in ways that might not be appropriate, while still letting the user get an answer through the session itself.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}