Who Can See a Claude Artifact Link?

The direct answer

It depends on which of Claude's two sharing paths made the link.

A published artifact: anyone with the link. Claude's publish button produces a public URL. There is no sign-in and no company check. Anyone who receives the link, whether you sent it to them or it was forwarded, can open the page. It can also be crawled or cached like any public page.

An org-shared artifact: teammates with a Claude seat. On Claude Team and Enterprise you can share an artifact inside your workspace. Now the audience is your Claude organization, but the gate is the Claude seat: a colleague without a Claude subscription in your org cannot open it.

What Claude does not offer is the setting most people assume they are getting: a link that only your company can open, using the accounts your company already runs, with no Claude seat required. That middle option exists, but it comes from publishing the artifact behind company SSO rather than through Claude's own sharing.

Who can open the link, by scenario

The distinction that matters for internal work is the last two rows: access tied to identity, not to possession of the link. For the concept behind that model, see what is gated publishing.

Why "anyone with the link" is riskier than it sounds

A public Claude artifact URL is unguessable, so people assume it is effectively private. The risk is not that someone guesses the address. The risk is what happens after you share it once.

• Forwarding. The first person you send it to can forward it to anyone. Because the page is public, every forward works, and none of them are stopped.
• No record. A public link has no viewer log. You cannot see who opened it or when, which is a problem for anything sensitive or regulated.
• Indexing and caching. Public pages can be crawled, cached, or captured. Once content is on the open web, you no longer fully control where it goes.

For a competitive analysis, a financial summary, or client work, "anyone with the link" is the wrong answer, even when the link is obscure. What you want is a link where an outsider hits a sign-in wall.

How to control exactly who can see the link

Publish the artifact to display.dev instead of relying on Claude's public link, and pick the audience per artifact.

Everyone at your company. Gate the artifact behind Google or Microsoft SSO. A viewer clicks the link, signs in once with their work account, and sees the page only if their email is on your company's domain. No Claude seat, no shared password, no new account. If the link is forwarded outside the company, the outsider cannot get in.

Specific people only. Add individual email addresses, including someone at a client or partner. They receive one-time code access to that one artifact without joining your organization.

Anyone, on purpose. If the artifact is meant to be public, set it public and share the link freely.

Getting the artifact from Claude to display.dev takes one of two forms. From Claude Desktop or Claude.ai, connect the MCP server and say "publish this to my team," and your agent returns a company-gated URL in the conversation. From Claude Code, the artifact is a file, so run dsp publish ./report.html. Both are covered on the share a Claude artifact page, and the company-only setup is stepped out in how to make a Claude artifact private.

Because access is tied to identity, Pro and Enterprise plans also keep an audit trail of who viewed which version, for 90 to 365 days. That is the record a public Claude link cannot give you.