Guide
How to share a Claude artifact, and who can see it
Updated 30 October 2026
In claude.ai, open the artifact, click Share, choose who has access and copy the link. Artifacts start private, and everyone who opens a shared one needs a Claude account; the exception is an older chat artifact made public with Publish, which anyone with the link opens. To share an artifact with a client or colleague who has no Claude account, and still keep it closed, publish it to ashare.net through a connector and open it to your company, specific emails or a password.
Share an artifact in claude.ai
- Open the artifact and click Share.
- On Team and Enterprise plans, add people from your organization and pick each one’s access level.
- Under Who has access, choose who else can open it.
- Copy the link and send it.
Access levels are Can view (open it and read comments), Commenter (also comment and download files the artifact offers) and Can edit. Sharing settings change only on the web and in Claude Desktop, not in the iOS or Android apps. Source: Share artifacts in Anthropic’s Help Center.
Are Claude artifacts public by default
No. An artifact is private to you until you share it. On Team and Enterprise plans it stays inside your organization by default, and an Owner decides whether members can share outside it at all.
Who can open a shared artifact
| Setting | Plans | Who opens it | Claude account |
|---|---|---|---|
| Only you | All | You | Yes |
| Invite by email (beta) | Pro, Max, Team, Enterprise | The person at that address; up to 50 people from outside your organization per artifact | Yes, under the invited address |
| Anyone at your organization | Team, Enterprise | People signed in to your organization | Yes |
| Anyone with the link | Pro, Max; Team and Enterprise once an Owner turns on External sharing | Anyone signed in to Claude who has the link | Yes |
| Publish (an artifact made in a chat before 16 September 2026) | Free, Pro, Max | Anyone with the link | No; asked to sign up only for features that use Claude |
Some details from the same article that decide whether an invite works for you:
- Claude doesn’t tell you whether an invited address has an account. Someone without one has to create it with that address first.
- Pending invitations expire after 30 days.
- Invitees can comment with Commenter access, but can’t mention people or ask Claude in a comment, and parts of the artifact that use Claude or your connectors don’t work for them.
- Docs, artifacts that connect to other websites, and artifacts with a file still being checked can’t be shared by email.
- On Team and Enterprise, sharing an artifact made in a chat also gives viewers the attachments and files of that chat.
Can a published artifact show up in Google
Anthropic’s sharing article doesn’t say. We opened one published chat artifact on 30 October 2026: claude.ai served it with an X-Robots-Tag: none header and a noindex, nofollow robots tag, which ask search engines not to index the page. That is an observation, not a promise in Anthropic’s docs. And noindex only keeps a page out of search results: anyone who gets the link can open it, forward it or post it somewhere that is indexed. Treat a public link as public.
Make an artifact private again
Open it, click Share and choose Only you (Pro and Max) or Only people invited (Team and Enterprise). For a published chat artifact, click Unpublish. Anthropic warns that you can’t publish it again afterwards, and that unpublishing deletes the data the artifact stored.
Share it with people who have no Claude account
ashare.net is a connector for claude.ai and Claude Desktop. Claude publishes the artifact’s HTML there and sets who opens the link. Readers confirm their email with a 6-digit code, or sign in with Google or Microsoft; they need no Claude account and create no account with ashare either.
Add the connector once:
Customize → Connectors → + Add → Add custom connector
Name: ashare
URL: https://ashare.net/mcp
Authentication: Sign in when needed
OAuth client: Register automaticallyThen Connect, sign in with your email and Allow. On Team and Enterprise an Owner adds the connector in Organization settings → Connectors, and members press Connect. On Claude’s Free plan you get one custom connector. Details: claude.ai and Claude Desktop.
Now ask Claude in the chat with the artifact:
Publish this artifact to ashare and share it with lena@client.ioOr pick another kind of access:
- Your company: “share it with the company” lets in everyone who signs in with an email on your company domain.
- Specific people: up to 100 emails per document, each gets a letter with the link.
- A password: “make it public with a password, expiring in 14 days” lets in anyone with the link and the password, until that date.
A new document is private until you choose. Someone who isn’t on the list can ask you in, and you approve from the email. For private and company documents you see who opened it and when. ashare links are unguessable, and search engines don’t index documents.
Readers can select text and comment. Back in the chat, ask Claude to “go through the comments on the ashare document”: it reads the threads, publishes a fixed version at the same link, replies and resolves them.
What doesn’t carry over
- Parts of an artifact that call Claude, your connectors or the artifact’s shared storage run inside claude.ai only. On ashare the page is static HTML: its scripts and libraries from CDNs run, those calls don’t.
- An artifact made from a Docs, Slides or Design template isn’t a plain page. Export it first, a doc to Markdown or a design to standalone HTML, and publish that file.
- A React component has to become a self-contained HTML file first: see how to host a Claude artifact.
If everyone you share with is in your Claude Team or Enterprise organization, Claude’s own Share is simpler: there is nothing to add, and readers comment on the artifact in claude.ai. ashare is for readers outside it, or for when you want access per document set by company domain, email or password.
ashare.net: your agent publishes HTML or Markdown and you choose who opens it: your company, specific emails or a password. Readers comment, the agent fixes the document.
Connect your agent