Guide

How to share a Claude Cowork artifact with a client outside your organization

Claude Cowork artifacts are designed for the people inside your organization. Legacy live artifacts, created before 19 August 2026, can only be shared inside your organization, with no external or public link. Newer artifacts can use "Anyone with the link" or email invitations, but an artifact that connects to your apps or uses Claude cannot use an open link, and invited people outside your organization must sign in to Claude. To send a client a page that needs nothing from them, export a snapshot of the artifact and host it with LiveSend.

What Claude lets you share

Claude has changed its sharing model more than once this year, so check the date of whatever you read. Today, the picture from Claude's own support documentation is this:

  • Legacy live artifacts (Cowork, created before 19 August 2026) are shareable inside your organization only. There is no external link and you cannot pick recipients by person.
  • Newer artifacts can use "Anyone with the link" or an email invitation, subject to your plan and your administrator's settings.
  • Connected artifacts (those that use your apps or call Claude) cannot use "Anyone with the link", and artifacts that connect to outside websites cannot be sent to people outside the organization.

In every case the reader needs a Claude account unless the artifact was published publicly, which is exactly what a connected artifact cannot be.

The path to a client: send a snapshot

When the client should not need an account and the artifact cannot be public, the simplest route is to stop sharing the live artifact and share what it shows.

  1. Refresh the artifact so its data is current.
  2. Copy the artifact's HTML or download the file. The exact option depends on the Claude interface you use.
  3. Paste it into LiveSend, or drop the file. You get a permanent link.
  4. Add a password and an expiration date if the content is sensitive (Pro), then send the link.
  5. When the data changes, upload a new version. The link does not change, so you never resend it.

Every view is logged with the time, the approximate country and the time spent, so you know whether the client opened it.

What you give up

  • It is not live. The snapshot does not refresh itself and cannot read the client's data. If the page depends on live connectors, it will show what it showed at export.
  • Size. A 2MB cap per HTML file on Free, 5MB on Pro.
  • Branding. A small LiveSend watermark on the Free plan, removable on Pro. No custom domain yet.

Use it when: the client needs to read and interact with a result, not to query your data.

When to stay inside Claude

If your colleagues are the audience, share the artifact inside your organization. They get the live version on their own access, which is the point of a connected artifact. Move to a snapshot at the moment the audience stops being your organization.

Not a connected artifact? See the four ways to share a regular Claude artifact.

Frequently asked questions

  • Can I share a Cowork live artifact outside my organization?
    No. Claude documents that sharing of live artifacts stays within your organization, with no external or public links and no recipient selection by person. They also became a legacy format on 19 August 2026: existing ones keep working and can be shared inside the organization, but you cannot edit them in place.
  • Why can a connected artifact not use an open link?
    Because a shared artifact runs on the reader's access, not yours. When someone opens it, it connects to their connectors and data sources. An open link would send a stranger to an artifact that tries to read data they do not have. Claude therefore keeps artifacts that connect to your apps or use Claude away from "Anyone with the link".
  • Can I invite a client by email instead?
    Sometimes. Email invitations to people outside your organization have to be enabled in your organization settings (on by default on Team plans, off on Enterprise), and the invited person signs in to Claude with that email address. Artifacts that connect to outside websites cannot be shared this way. For many clients, asking them to create a Claude account to read a report is the real obstacle.
  • What does the client see in a LiveSend snapshot?
    The page as it was when you exported it, with its scripts, charts and layout. It is a snapshot: data that came from connectors is frozen at that moment, so refresh the artifact before you export. Re-export when the data changes. On LiveSend a new version keeps the same URL.
  • Is it safe to move an artifact out of my organization?
    That depends on what is in it. A snapshot contains whatever the artifact displayed. If it shows customer data or anything covered by an internal policy, check the policy before you send it, and use a password and an expiration date on the LiveSend link (Pro).

Related guides

Want to try the LiveSend approach?

Paste your HTML, get a permanent link. Free for the first 3 documents.

Get started free