Claude Artifact Link Not Working? 8 Reasons and Fixes
If someone can't open a Claude artifact you shared, the most likely reason is that they aren't signed in to Claude. Since Anthropic rebuilt artifact sharing in 2026, a newer claude.ai artifact shared with "Anyone with the link" only opens for people with a Claude account. Anthropic's help center says so directly: "People without one can't open a shared artifact, even with the link." Older published chat artifacts and Claude Code public links don't have that requirement, which is why the same kind of link can work for one person and not for another.
Find the symptom below, then jump to the fix.
| What the viewer sees | Most likely cause | Fix |
|---|---|---|
| A Claude sign-in or sign-up page | They have no Claude account (newer claude.ai artifact) | Cause 1 |
| Signed in, but no access | Shared inside your organization only | Cause 2 |
| "Anyone with the link" is missing or greyed out for you | External sharing is off on Team or Enterprise | Cause 3 |
| Invited, but the invitation won't open | Signed in with a different email, or it expired | Cause 4 |
| You can't choose "Anyone with the link" for one artifact | The artifact connects to apps or uses Claude | Cause 5 |
| A link that used to work has stopped | An admin changed a setting | Cause 6 |
| The page doesn't exist | Unpublished, deleted or removed by retention | Cause 7 |
| The page opens but sections show errors | Live data uses the viewer's own access | Cause 8 |
First, which kind of artifact did you share?
Claude has three kinds of artifact, and each one follows different rules. The link tells you which kind you have:
- Legacy chat artifact. Made in a chat before 16 September 2026, shared with the Publish button. A published one opens for anyone, no account needed.
- Newer claude.ai artifact. Shared from the Share menu. Viewers need a Claude account.
- Claude Code artifact. The link contains
claude.ai/code/artifact/. A public link opens without signing in.
The full comparison is in are Claude artifacts public.
1. The viewer doesn't have a Claude account
This is the most common cause. For newer claude.ai artifacts, "Anyone with the link" means anyone signed in to Claude who has the link. Anthropic's wording: "Everyone needs a Claude account." A client, a manager or a friend who has never used Claude lands on a sign-in page instead of your artifact.
Fix. Pick one:
- Ask them to create a free Claude account, then open the link again.
- If it's a Claude Code artifact, share it to a public link instead. Anthropic documents those as opening "with no claude.ai sign-in required".
- Publish a copy of the content somewhere that doesn't need an account. Copy the artifact into a file and publish that file. The steps are in the artifact workaround cookbook.
2. The artifact is only shared inside your organization
On Team and Enterprise plans, sharing with "Anyone at [your organization]" or with named colleagues only works for people signed in to that organization's Claude account. "Only people signed in to your organization can open it." Someone using a personal Claude account, or a different company's, gets no access even though they're logged in.
Fix. Ask them to switch to the organization account in Claude. If they're outside the company, invite them by email (Cause 4), or use "Anyone with the link" if your workspace allows it (Cause 3).
3. External sharing is off for your workspace
On Team and Enterprise, "Anyone with the link" stays unavailable until an Owner turns on External sharing under Organization settings > Artifacts. If the option is missing or greyed out, Anthropic's guidance is the same in both cases: "ask an Owner or Primary Owner."
Fix. Ask an Owner to do one of two things:
- Turn on External sharing for the workspace.
- Leave it off and allow just this one artifact. The admin guide allows this for an artifact already shared with the organization or with invited people.
The second request is usually easier to get approved. More detail is in sharing Claude artifacts on a Team plan.
4. The invitation went to a different email, or expired
Email invitations (beta, up to 50 outside people per artifact) only work for the exact address you invited. The invitee opens the email, clicks "View invitation", signs in with that address, and then clicks "Accept and open." Signing in with a different Google account or a work alias won't work.
Pending invitations also expire: "Pending invitations expire after 30 days." Accepted ones don't.
Fix. Check which address the invitee signed in with, or send a new invitation to the address they actually use. If the invitation is more than 30 days old and was never accepted, invite them again.
5. The artifact connects to apps or uses Claude
Some artifacts can't be shared by link at all. Per Anthropic, artifacts that "connect to your apps or use Claude" can't use "Anyone with the link", and email invitations are restricted for them too. A dashboard that reads from your Google Drive, or a tool with a button that asks Claude something, falls into this group.
Fix. Ask Claude to make a static version, with the data written into the page and no AI-powered controls, and share that. If the reader only needs to see the result, a copy published as a file works too.
6. An admin changed a setting after you shared
A link that worked last week can stop working without you changing anything:
- Turning off External sharing "stops existing public links from working until you turn it back on," except for artifacts allowed individually.
- Turning off email invitations locks out people you already invited until it's turned back on.
- On Team and Enterprise, changing an artifact's access to "Only you" removes outside invitations.
- If the person who sent an invitation leaves the organization or loses edit access, their pending invitations stop working.
Fix. Ask an Owner what changed. Access usually comes back when the setting does. If the link has to stay up regardless of workspace policy, publish a copy outside Claude.
7. The artifact was unpublished or deleted
Unpublishing a legacy chat artifact revokes access, and it can't be reversed: "You can't publish an artifact again after you unpublish it." Deleting a newer or Claude Code artifact ends the link for everyone, including you. On Enterprise, a retention policy can permanently delete artifacts nobody has opened for a set period.
Fix. There's no way to bring back the same link. Create the artifact again (ask Claude to rebuild it from the conversation) and share the new link.
8. The page opens, but live sections are empty
Artifacts that pull data through connected apps or MCP connectors make those calls with the viewer's account, not yours. "Viewers use their own access." If the viewer hasn't connected that app, doesn't have access to the data, or declines the permission prompt, those sections show an error instead of your data. For Claude Code artifacts, connector calls don't run at all for someone who opens a public link without signing in.
Fix. Tell the viewer which app to connect, or ask Claude to rebuild the page with the current data written into it so nothing depends on the viewer's access.
Has Claude fixed the shared artifact problem for Team plans?
Partly. In early 2026 a Team plan user couldn't share an artifact outside the organization at all. Now they can invite outsiders by email without an admin, and an Owner can turn on public links. What hasn't changed is that newer claude.ai artifacts need a Claude account to view. If your problem was clients who don't use Claude, that part still isn't fixed natively.
The fix that removes most of these causes
Six of the eight causes come from where the artifact lives: Claude accounts, organization settings and connector access. Moving a copy to a plain web link removes all six. Copy the artifact, save it as a file, publish it:
pbpaste > deliverable.html
anchorify deliverable.html
# → https://anchorify.io/your-org/your-project/deliverable
Anyone with the link can open it without an account, and it's hidden from search engines unless you choose otherwise. Re-publishing the file updates the page at the same URL. You can add --password or --access comment if you need them. Check your company's policy on hosting outside Claude before doing this for work content. The step-by-step for each artifact type is in the workaround cookbook.
Frequently Asked Questions
Why does my Claude artifact ask people to sign in?
Because newer claude.ai artifacts require every viewer to be signed in to Claude, even with "Anyone with the link." Anthropic's help center: "People without one can't open a shared artifact, even with the link." Published legacy chat artifacts and public Claude Code artifact links are the exceptions and open without an account.
Why does "Anyone with the link" not show up for me?
Either you're on a Team or Enterprise plan where an Owner hasn't turned on External sharing, or the artifact connects to your apps or uses Claude, which can't be shared by link at all. Ask an Owner or Primary Owner in the first case. In the second, share a static version of the artifact.
Why did my Claude artifact link stop working?
An admin may have turned off External sharing or email invitations, which suspends existing links until the setting comes back. It may also have been unpublished, deleted, or removed by an Enterprise retention policy, and those can't be undone. Ask an Owner first, because a setting change is the reversible case.
Can I share a Claude artifact on mobile?
You can open and use artifacts on mobile, but Anthropic says you can't change sharing settings in Claude for iOS or Android. Change who has access from the web or desktop app.
My colleague is signed in. Why can't they open it?
They're probably signed in to a different Claude account from the one your artifact is shared with. Org-shared artifacts need the organization's account, and email invitations need the exact invited address. Ask them to check which account they're using in Claude.
Sources
- Publish and share artifacts, Claude Help Center: who can open a shared artifact, invitations, artifacts that can't be shared outside the organization, and unpublishing.
- Artifacts admin guide for Team and Enterprise plans, Claude Help Center: External sharing, per-artifact exceptions and what happens to existing links.
- What are artifacts and how do I use them, Claude Help Center: the 16 September 2026 cut-off for legacy artifacts.
- Share session output as artifacts, Claude Code Docs: public links with no sign-in, and connector calls for viewers.
When a Claude link keeps hitting sign-in screens and admin settings, Anchorify publishes the same content at a link anyone can open. Free during beta, and readers never need an account.