You asked Claude to build something — a dashboard, a proposal, a report — hit Share, and sent the link to a client. They replied that it asks them to log in, or that they get nothing at all.
Nothing is broken, and you haven't missed a setting. On Claude's Team and Enterprise plans, sharing an artifact makes it available within your organisation only, and viewers have to authenticate with an account in that organisation. Anthropic's help centre states plainly that artifacts on those plans cannot be published publicly — see Publishing and sharing artifacts (checked August 2026).
Why the plan you're on changes the answer
This is the part that catches people out, because the button looks the same either way.
- Free, Pro and Max have publishing. The artifact gets a public URL and anybody who opens it can see it, no account required.
- Team and Enterprise have sharing. The artifact becomes visible to members of your organisation, who must be signed in to that organisation to view it.
So the same action, in the same panel, produces a public page for an individual subscriber and an internal-only page for a company. If you upgraded a personal account to a Team plan, a workflow that used to work for clients quietly stopped working.
The same rule applies to whole conversations: on Team and Enterprise, a shared chat goes to colleagues in your organisation, not to the outside world.
This is a sensible default. Company accounts hold company work, and silently public-by-default would be much worse. It just isn't what you want when the audience is a client.
Things people try that don't help
- Re-sharing the link. The restriction is on the plan, not the link, so a fresh link behaves identically.
- Asking the client to make a free Claude account. They'd need an account in your organisation, which means a seat you're paying for, and access to more than you intended.
- Screenshotting it. Works for a static chart, throws away every filter, tooltip and tab — the reasons you built an interactive page at all.
- Sending the raw
.htmlfile. Email quarantines it, Slack shows a paperclip, and if it does arrive it often opens as a blank page.
What actually works
The artifact is, underneath, a self-contained HTML file. Once you have that file, publishing it somewhere that issues public URLs solves the problem in one step.
With Pagepost that's either of:
- From the chat. With the Claude connector set up, ask Claude to publish the artifact to Pagepost. You get a link back in the conversation.
- By hand. Copy the artifact's code, save it as a
.htmlfile, and drop it on pagepost.app. Same result, no setup.
Either way the page keeps its scripts and styling, so charts and filters still work for the person opening it.
If it's org-only for a reason
Sometimes the restriction is doing its job and the content genuinely shouldn't be on a public URL. Making it public anyway is the wrong fix, so it's worth being deliberate:
- Restrict it to your Slack workspace instead of anyone-with-the-link, if the audience is internal but Claude's organisation isn't where they live.
- Set an expiry so a link for one meeting stops working afterwards.
- Revoke it the moment the engagement ends — the URL stops resolving, and you can check the view count first to see whether it was ever opened.
That's a different trade-off from Claude's, not a strictly better one. Claude's org-only sharing enforces access through accounts you already control, which is stronger than an unguessable URL. If your requirement is genuine authentication rather than convenient delivery, keep the work inside Claude and send the client a summary instead.
The short version
Sharing an artifact on a Team or Enterprise plan is internal by design and can't be made public. To get an interactive page in front of someone outside your company, publish the underlying HTML to a URL that doesn't require an account — then use expiry and revocation to put the boundary back where you want it.
If you're weighing the two approaches more generally, the side-by-side comparison covers cost, control and what happens to the link afterwards.