To share a Claude Cowork artifact with a client or anyone outside your organization, ask Claude for the page as one HTML file with the data written into it, host that file on Hostus and send the link: the client needs no Claude account, no sign-in and no connectors, and you update the same link when the numbers change.
Two things stop a Cowork artifact at your organization's edge. A live artifact's sharing stays inside the organization, and live sections run on the viewer's own data sources, so an outsider sees errors even when a newer artifact's link opens for them. The facts below are from Anthropic's live artifacts article and Share artifacts article, read on 7 November 2026.
What Anthropic says about sharing Cowork artifacts
- Live artifacts are the old kind. They are artifacts made in Cowork before 19 August 2026. They keep working and you can open and share them, but you can't edit them in place.
- Their sharing stays inside your organization. The article says there are no external or public links and no per-person recipient selection: anyone in your organization who has the link can open it.
- To change one, you republish it. Open it, click Share and republish it as a new artifact. People with the existing link see the new version without a new link, and from then on it works like any other artifact.
- Newer artifacts follow the general rules. Artifacts made on or after 19 August 2026, and live artifacts you republish, work like any other artifact. On Team and Enterprise, "Anyone with the link" is available only when an Owner has turned on External sharing or allowed that artifact. With the link, most artifacts open without a Claude account, but someone who opens it from outside your organization, or without signing in, gets no connected apps and no Claude features, and can't see data the artifact saved. Artifacts that connect to other websites can't use a public link at all.
- Live data uses the viewer's access. A shared artifact connects to the viewer's own connectors and data sources. If the viewer can't reach a data source, that part of the page shows an error instead of your data.
For a teammate with the same tools, that last rule is a feature: everyone sees their own numbers. For a client, it means a page full of errors.
Why a client sees errors, an empty page or nothing
| Layer | On Hostus | Inside your organization | A client outside it |
|---|---|---|---|
| Who can open the link | Anyone you choose: public, an email list, a domain | Your organization | Live artifact: nobody outside. Newer artifact: only if External sharing is on or the artifact is allowed |
| Account needed | None, on any page type | Your organization's Claude account | None for most artifacts; docs need sign-in |
| Live data | The data Claude wrote into the page | Pulled through each viewer's connectors | Errors where the data should be: connected apps don't run for outsiders |
| Saved data and forms | Work for every reader, no account | Shared storage, for signed-in members | Hidden until they sign in, then read-only |
| Updating | Same link, new version, last 20 kept | Republish a live artifact as new | Nothing reaches them |
How to send a Cowork artifact to a client
- Ask Claude for a portable version. In the same Cowork task, ask for the page as a snapshot:
Rebuild this artifact as one self-contained HTML file for a client outside our company.
Write the current numbers into the page as data, with no connector calls and no sign-in.
Keep each part under its own h2 heading, add the date the data was pulled at the top,
and keep the charts as inline SVG.- Publish it. If you added the Hostus connector to Claude, say "publish it to Hostus" and Claude uploads it. Otherwise download the file and drop it on hostus.io.
- Gate it to the client. The document starts private. In the dashboard, set it to Email-gated and limit it to
@clientcompany.com, so only addresses at their domain can be typed into the gate. The gate does not verify the address; for named people only, make it Private and invite them. - Send the link,
your-slug.hostus.page. It opens on a phone, with no app and no account. - Refresh it on the same link. Next week, ask Claude to rebuild the snapshot with the new data and update the same Hostus document. The client's link doesn't change, and the History tab keeps last week's version to compare or restore.
The pattern is the same as a monthly client report. Here is one, live: a fictional studio's performance report with KPIs, an SVG chart and a section per topic, the kind of page a Cowork dashboard becomes when it leaves the building.
What the client gets that a Cowork link can't give
- No account, no sign-in, no connectors. The page carries its own data, and its forms work for the client.
- Reading by section. You see that the client spent four minutes on the forecast and ten seconds on the methodology, per reader on a gated page.
- Questions to the document. The client can ask the page a question and get an answer from its own text that cites the section, and you see what they asked.
- Replies on a section. "Agree with the forecast, not the hiring plan" lands next to the section it is about, in a private conversation with you.
- A form that works. An approval or a feedback form in the page stores responses on the document and emails each one to you.
Which way should you share it?
Hostus. Best if the reader is outside your organization: a client, a partner, an investor. A snapshot with the data in it, one link that survives every refresh, an email gate to their domain, and you see what they read. Free for 20 documents.
Keep it in Cowork. Pick it if everyone who opens it is in your organization and has the same connectors. Live data per viewer is exactly what an internal dashboard wants.
A PDF export. Pick it if the client must file it somewhere. It is a dead end for questions, forms and reading data, and every update is a new attachment.
Good to know before you switch
A hosted page is a snapshot: it shows the data Claude wrote into it until you update it, it does not pull from your connectors. Hostus has no custom domain: every page lives at your-slug.hostus.page and carries a small "Published with Hostus" badge in the corner, on the free and the paid plan. Public pages are noindex, so they do not show up in Google. It hosts HTML files with their images, video and fonts, not PDFs or framework builds, so ask Claude for one self-contained HTML file. The free plan is 20 documents, 2 MB in total and 100 form responses a month (responses past that are kept and unlocked on a paid plan); paid is $9.99 a month or $49.99 a year. An email gate identifies readers, it does not verify the address: for a page that must stay between you and named people, use invite-only.
If the report should stop working after a project ends, Claude can set an expiry date of up to 90 days when it publishes through the connector; after that the link answers "expired" and the document is deleted.