Claude artifact: Page not found.

What the screen is hiding

The page looks like a broken link. It is not. The artifact exists, the URL is right, and the sender can open it fine. Claude answers every request it will not serve with the same not-found page, so a permission problem and a deleted page look identical from where you are standing.

That is the screen from a client's Slack channel, opened by a contractor who is not in the client's Claude organisation. The artifact was fine. The audience setting was the problem.

The three causes

1. It was shared with the organisation, not with you. On Team and Enterprise plans an artifact can be shared with "Only people with access" or "Everyone in your organization". Both check the account you are signed into. If your account is not in that organisation, or you are not signed in at all, you get the not-found page. This is the common case, and it is the default a colleague picks when they want to share "internally".
2. External sharing was switched off. On Enterprise, public links only work while an Owner has external sharing enabled for the organisation. Anthropic's help centre is explicit that turning it off later stops every existing public link until it is turned back on. A link that worked last week and died this week, with nothing changed on the artifact, is usually this.
3. It was unpublished. Unpublishing is permanent. The link dies, the artifact can never be published again, and any storage it used is deleted. The sender would have to create a new artifact.

A fourth, smaller one: you are signed into a different Claude account than the one the sender expects. If you have both a personal account and a client-issued one, switch and try again before sending the message below.

Why it keeps happening to contractors

Sharing inside Claude is built around the organisation. On Team and Enterprise, the choices are people in the org, everyone in the org, or the public. On Pro and Max, the only way to share is a public link. There is no "share with this one person outside the company" option, and Claude Code artifacts follow the same rule: private to the author until shared, then shared with the org or with the world.

So the person at the client does the sensible thing, keeps it internal, and sends you the link. They see the page. You see the 404. Nobody did anything wrong, and the system has no setting that describes your relationship to the company.

What to ask the sender for

Send this back: "I can't open artifacts shared inside your organisation. Could you publish it to Stacktree and send me that link?"

What that costs them depends on where they work:

• Claude Code, Codex or Cursor. The sentence is enough. Those agents can make the request themselves, no account and no key, and hand back a private link that opens for you with no login.
• claude.ai chat. The chat cannot call an outside service on its own; we tested it, and it says so. They add the Stacktree connector once, a single paste of a URL into Claude's connector dialog, then ask Claude to publish the artifact. From then on it is one sentence for every future page.
• Neither, or no time. Ask for the HTML file. Then publish it yourself in a minute and you hold the link, which means the next change to their org settings cannot break it.

Whichever route, the link you get back is private, opens in any browser without an account, and can carry a passcode or a company email gate if the content warrants one. If you are the one who will send it onward to your own client, it can sit on your domain too.

Why not "Anyone with the link"

It is the quickest fix and the wrong one for most of what gets shared this way. A public artifact opens for anyone, and it can be indexed. A search of the public artifact address on claude.ai turns up clinical trial summaries with per-patient results, client onboarding policies, fiscal compliance dashboards, stock predictions, all published by people who almost certainly meant them for a handful of readers. On Team and Enterprise the switch also needs an Owner to have enabled public sharing at all, which is a conversation your contact may not want to start for one file.

A private link solves the problem the sender actually has, getting one page to one outsider, without turning the page into a search result.

If you are the sender

The contractor cannot fix this from their side, so the message above will keep arriving until the page lives somewhere that does not check for an org account. Publish deliverables meant for outsiders on a private link from the start, keep the Claude artifact for the internal audience, and you stop being the reason someone sees that screen.