The short answer, in three parts
The answer depends on whether you’ve shared it, and with whom.
- Before you share: yes. Every artifact starts private to the person who made it.
- After you share: it opens for the people your setting allows, and each of them needs a Claude account. “Anyone with the link” means anyone with the link and a Claude account.
- For someone without Claude: a shared artifact doesn’t open, even with the link. The one exception is a legacy artifact published from a chat.
What a client without Claude can open
The booking app below was made for a climbing gym and shared with the gym by Email. Book a session, then cancel it from Bookings.
Nothing in it needs Claude. It’s a web page that runs in any browser.
Claude’s sharing options by plan
As Claude’s help center described them on October 5, 2026:
| Plan | Who you can share with | Does the viewer need a Claude account? |
|---|---|---|
| Pro and Max | “Only you” or “Anyone with the link”. To reach specific people, invite them by email. | Yes |
| Team and Enterprise | “Only people invited”, “Anyone at [organization]” or “Anyone with the link”. The last works only when an Owner has turned on External sharing, or has allowed that one artifact. | Yes |
| Email invitations (beta) on Pro, Max, Team and Enterprise | Up to 50 outside people per artifact, each as Can view, Commenter or Can edit | Yes, under the invited address |
| A legacy artifact published from a chat (Free, Pro and Max) | Anyone who has the public link | No. They’re asked to sign up only for features that use Claude |
Some artifacts can’t be shared every way:
- Not by link: artifacts that connect to your apps or use Claude, and on Team and Enterprise, docs.
- Not by email: Claude Docs documents, artifacts that connect to other websites, and artifacts with an uploaded file still being checked.
- For invitees: the parts that use Claude or your connectors don’t work.
Legacy artifacts and new ones
Artifacts made in a chat before September 16, 2026 are legacy artifacts. You can tell by the button: they show Publish or Share & copy link where newer ones show Share.
On Free, Pro or Max, publishing a legacy artifact gives you a public link. Anyone can view and use it without a Claude account, and is asked to sign up only for features that use Claude. You also get an embed code, with a list of the domains allowed to embed it.
Email invitations and their limits
You can also invite specific people by email in Claude, with these conditions:
- They’re in beta, on Pro, Max, Team and Enterprise.
- Each person gets one of three access levels: Can view, Commenter or Can edit.
- Up to 50 outside people per artifact.
- Pending invitations expire after 30 days.
- The invitee needs a Claude account under the invited address.
Claude doesn’t tell you whether the person you invited has an account, and its help center doesn’t describe a way to see who opened the artifact.
Team and Enterprise: sharing outside the organization
- Inside the organization: “Anyone at [organization]” opens it for your colleagues.
- A link for anyone: works only when an Owner has turned on External sharing, or has allowed that one artifact. Viewers still need a Claude account.
- Invitations outside the organization: on by default on Team plans, off by default on Enterprise.
On Enterprise, if you can’t invite a client, ask an Owner whether outside invitations are on.
What the help center doesn’t describe
Three things client work often needs aren’t on Claude’s sharing page:
| You want | Claude’s help center | artifact.guru |
|---|---|---|
| To know who opened it | Not described | Views counts opens and visitors on every link for the last 30 days, and names people on Private and Email links |
| Your own domain | Not described | Public and Secret code links open on your subdomain, such as docs.yourstudio.com |
| Earlier versions | Not described | Every publish or edit is a version at the same link, and Roll back brings an old one back |
When Claude’s own sharing is the right choice
Stay in Claude when everyone already has it, or when you need something artifact.guru doesn’t do. Claude’s invitations offer Commenter and Can edit; artifact.guru has no comments and no co-editing. And if the artifact uses Claude itself, that part runs only in Claude. There, each person signs in with their own Claude account and the usage counts against their plan. The sharing limits above still apply.
| Situation | Use |
|---|---|
| Everyone who needs it is in your Claude organization | Claude: “Anyone at [organization]” |
| They have Claude, and you want their comments or edits | Claude: an email invitation as Commenter or Can edit |
| The artifact calls Claude or your connectors | Claude: those parts run only there |
| A client without a Claude account, by name | artifact.guru: Email, and their name shows in Views |
| A board or a client team, without accounts | artifact.guru: Secret code, lasting 7 or 30 days, or with no expiry |
| Anyone at all, at your own address | artifact.guru: Public, on a custom domain |
Publish it for people without a Claude account
artifact.guru gives the artifact its own link that opens in any browser. You choose who can open it.
- On Team or Enterprise, ask an Owner first
Only Owners and Primary Owners can add a custom connector there (on Enterprise, also people with a custom role that includes “Manage access to Libraries”). On Pro, Max and Free, skip this step.
- Add the connector, or connect to it
In Claude, open Settings → Connectors, choose Add custom connector, name it artifact.guru and paste the address. Free allows one custom connector. On Team and Enterprise, connect to the one your Owner added.
Copyhttps://mcp.artifact.guru/mcp - Approve
Your browser opens. Sign in to artifact.guru, tick the workspaces Claude may use and approve.
- Ask Claude
In the chat with the artifact, say: “publish this artifact to artifact.guru and invite ana@client.com”. Claude sends the artifact’s source and replies with the link, set to Email for that address.
- Send the link yourself
artifact.guru doesn’t email Ana an invitation. Paste the link into your own email or chat.
You need a Individual plan ($12 a month) or a Team plan. Ana needs no plan and no password.
What the client sees
- She taps the link on her phone
A card says Sign in to open, because it was shared with specific people. She signs in with the address it was sent to.
- She gets a one-time code
She types ana@client.com and a code arrives by email. If she’s new, she creates an account in the same step, with no password.
- The app opens
It runs under a slim bar with the title, Copy link and Download. To show it full screen instead, switch off Show controls.
Someone signed in with a different address sees You don’t have access. Views lists Ana as “Not opened yet” until she opens it, and by name after that. For a group without accounts, a Secret code works better. They type the code and the page opens. See Choose who can open your link.
Limits
- No comments and no co-editing. Changes come from you or your agent, as new versions at the same link.
- No invitation emails and no alerts when someone opens a link. You send the link and check Views in the app.
- No server behind the page. Forms store nothing, and what a page saves resets when it reloads.
- One HTML page or React component can be up to 5 MB, and each artifact can have up to 50 invited addresses.
