How do you make a Claude artifact private, and send it to one client?

Who can open a shared Claude artifact, plan by plan, how to stop sharing one, and how to send one privately to a client who doesn’t use Claude.

On this page

By Kaz Kato · Published 12 October 2026 · Updated 12 October 2026

A Claude artifact is private until you share it. Shared from Claude’s apps, it opens for people signed in to Claude, by link, invitation or inside your organisation. Claude Code can also publish one to a public link, open to anyone. To send one to one client, privately, deploy it to a room on their own link.

This guide covers Claude’s own settings for artifacts you make in Claude’s apps, plan by plan. It says who can open a shared artifact, what changes when an artifact uses Claude, and how to stop sharing one. Then it shows the private route for a client. If you are choosing between tools rather than settings, five ways to share an artifact with a client compares them. If artifacts are new to you, what a Claude artifact is starts at the beginning.

Is a Claude artifact private?

Yes, until you share it. A new artifact opens for you alone. Sharing changes that, and every way Claude’s apps offer asks the person opening it to sign in to Claude. The exceptions are an older kind of artifact nobody can make any more, and a public link from Claude Code.

A Claude artifact starts private to the person who made it. Nothing is shared until they share it.

Anyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. Claude calls artifacts made in a chat before 16 September 2026 legacy artifacts. They still work and can still be published, but no new ones can be made.

So for anything you make in Claude’s apps today, the people you share it with need a Claude account. Claude Code is different. Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. Someone who opens a Claude Code artifact’s public link without signing in, or from outside your organisation, sees the label “Content is user-generated and unverified” instead of your name.

Who can see it once you share it?

It depends on the setting you choose and on your plan. On Pro and Max, you choose between anyone with the link and people you invite by email. On Team and Enterprise, artifacts stay inside the organisation unless an owner allows more. From Claude’s apps, everyone who opens one is signed in to Claude.

Setting Who can open it Needs a Claude account Plans What you learn about who opened it
Not shared Only you — Every plan —
Anyone at your organisation People signed in to your organisation Yes Team, Enterprise No record is described
Anyone with the link Anyone signed in to Claude who has the link Yes Pro and Max; Team and Enterprise if an owner allows it No record is described
Invite by email Only the people you invite Yes, with the address you invited Pro, Max, Team, Enterprise Claude doesn’t tell you whether they have an account
A published legacy artifact Anyone with the link No Free, Pro, Max; none made since 16 September 2026 No record is described
A public link from Claude Code Anyone with the link No Pro and Max; Team and Enterprise if an owner allows it No record is described
A Roomi private link (ours) The person you named, and anyone they say they passed it to No Pro and up Each visit, the time on each screen, the tour and their answers

What each row rests on:

  • Anyone with the link. Sharing an artifact with “Anyone with the link” is on Claude’s Pro, Max, Team and Enterprise plans, not on Free. From Claude’s apps, whoever opens the link must still be signed in to Claude.
  • Inside your organisation. On Claude’s Team and Enterprise plans, artifacts stay inside the organisation by default. “Anyone with the link” works there only when an owner has turned on external sharing, or allowed that one artifact.
  • Invite by email. A Claude artifact can be shared with anyone who has its link, or with people you invite by email. An invitation works only for the person invited. You can invite up to 50 people from outside your organisation to one Claude artifact. Pending invitations expire after 30 days; accepted ones do not expire.
  • On Free. On Claude’s Free plan, the help page’s sharing table lists one option: publishing a legacy artifact made in a chat. Since no new legacy artifact can be made, the table gives a Free account no way to share one made today.
  • A public link from Claude Code. It needs no sign-in, as above. People who reach a Claude Code artifact only by its public link do not see its comments, and cannot add any.
  • Who opened it. When you invite someone to a Claude artifact, Claude doesn’t tell you whether they have an account. Its help page on sharing describes no record of who opened one. Claude Code’s artifacts page describes no record of who opened an artifact, no expiry date and no guided tour. For anyone outside your organisation, it describes a public link, not one for a named person.

What about artifacts that use Claude or your apps?

They are the most private of all, whether you want that or not. An artifact that calls Claude, or reads from your connected apps, cannot be shared by link from Claude’s apps. People you invite from outside your organisation find those parts do not work. Everyone who does open it uses their own access and their own Claude plan.

On Claude’s Pro and Max plans, an artifact made in Claude’s apps can be shared with “Anyone with the link”, or with people you invite by email. One that connects to your apps or uses Claude cannot be shared by link.

For people invited from outside your organisation, the parts of a Claude artifact that use Claude or your connectors do not work. Someone opening a shared Claude artifact uses their own access. An artifact that reads from connected apps uses the viewer’s connections, and shows an error where they have none.

An artifact that calls Claude costs its maker nothing. Each person using it signs in with their own Claude account, and their use counts against their own plan.

Check one more thing before you share. Some Claude artifacts save information that everyone who opens them can see, such as a shared tracker. Claude advises checking for that before you enter anything sensitive.

How do you stop sharing it?

Open the artifact, choose Share, and set who has access back to the narrowest option your plan offers. On Pro and Max that does not remove the people you invited by email, so remove each of them too. A published legacy artifact is unpublished instead, and that cannot be undone.

To stop sharing a Claude artifact, choose “Only you” on Pro and Max, or “Only people invited” on Team and Enterprise. On Pro and Max, people you invited by email keep their access until you remove each one.

Unpublishing a legacy Claude artifact revokes its public link. It cannot be published again, and any data it stored is deleted for good.

Claude’s help page on sharing describes no expiry date for an artifact shared by link. Only pending email invitations expire. So a link you send stays open until you change the setting.

Send it privately to a client who isn’t on Claude

In Claude’s apps, a client who does not use Claude is asked to make an account before they see your work. A Claude Code public link needs none, but anyone with it can open it, and its page describes no record of who did. A room needs no account either: the client opens their own link in a browser, and you choose when it closes.

  1. Add the connector. Custom connectors work on every Claude plan, Free included; Free is limited to one. The Roomi connector is one. Deploying from Claude has the address and the three steps.
  2. Say “deploy it to roomi” in the chat where you made the artifact. Claude writes it out as files a browser runs, with an index.html at the root.
  3. Swap anything that calls Claude for sample answers. Nobody outside your Claude account can use those parts, so ask Claude to replace them with canned replies.
  4. Read the rehearsal. Claude checks the files and shows you what would go live. Nothing is published until you say yes.
  5. Make a link for your client. On Pro, ask Claude for a viewer link in their name, with an expiry if you want one.
  6. Send it yourself. Roomi sends nothing. In your message, say who you are and how to reach you. Say too that the room records what they do there and shows it to you, as the terms ask.

The link carries their name, and you can revoke it at any moment. A revoked or expired link answers with a plain “Not found”, the same as a link that never existed. Sharing a private link covers every option.

Claude’s sharing or a room

Use Claude’s own sharing for colleagues and anyone who already uses Claude. It is the quickest way to put an artifact in front of them. Use a room for a client or a prospect you want to follow up. They need no account, they get a link of their own and a guided tour, and you see what they looked at and who they passed it to. Pricing shows what each plan includes. Sharing a Claude prototype with a client takes the room route step by step.

Questions people ask

Can someone open my shared artifact without a Claude account?

Anyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. No new one of those can be made. An artifact Claude Code publishes to a public link needs no sign-in at all.

Does Claude show who opened it?

Claude’s help page on sharing artifacts describes no way to see who has opened one. A room on Roomi’s Pro plan shows each person’s visits, their time on each screen and what they answered.

Claude’s help page on sharing describes no expiry date for an artifact shared by link. Only pending email invitations expire. A Roomi private link can close after the number of days you choose, or be revoked at any moment.

Will a client see my chat?

On Claude’s Team and Enterprise plans, sharing a legacy artifact made in a chat also gives its viewers the attachments and files in that chat. Check the chat for anything sensitive before you share what you made in it.

Will an artifact that calls Claude cost me when others use it?

An artifact that calls Claude costs its maker nothing. Each person using it signs in with their own Claude account, and their use counts against their own plan.

Sources

About the author

Kaz Kato, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit.

Send it to one client, not to everyone with the link.

Add Roomi to Claude and say “deploy it to roomi” in the chat you made it in. It starts free.

Get started freeSee pricing