How to Share a Claude Artifact Privately

Claude made you an artifact: a slide deck, a one-pager, a small dashboard as self-contained HTML. The obvious way to share it is a public link that anyone can open. For a throwaway demo that is fine. For a client proposal, a board update, or anything with numbers in it, “anyone with the link” is the wrong default.

The problem is that a Claude artifact link is all-or-nothing. There is no notion of “these three people, read only.” You want controlled access: send it to the client, not to the client’s whole company, and be able to take it back later.

You can. Host the artifact once, then choose who gets in:

• Grant read access by email so only named people see it, after they sign in.
• Or send a revocable, expiring share link when a login is too much friction.
• Update the artifact in place without minting a new link every time.

Prezzly does not generate the artifact. Claude does. Prezzly hosts it and controls who can open it.

Why a raw artifact link is all-or-nothing

An artifact URL is a bearer secret: whoever holds it, opens it. That has real downsides for anything client-facing:

• No audience. You cannot say “only Anna and the CFO.” You can only say “the internet, if they guess or get forwarded the link.”
• No takeback. Once it is out, it is out. Forwarding is invisible to you.
• It lives inside a chat tool. Copy the code out, paste it somewhere, and now there are three stale copies.

If you have not moved the artifact off the chat yet, start there: send them as a hosted link so you have one URL you actually control, then decide who can open it.

Option A: grant access by email (private, no public link)

The tightest option is to not hand out a public link at all. Upload the artifact to your library, then grant a specific email read access to that presentation. The recipient signs in and finds it under Shared. No token floats around in a chat log.

This is the right mode for:

• A proposal that should reach one client contact, not a forwarded thread.
• An internal deck for a named group.
• Anything you want to revoke cleanly later by removing the grant.

Access is read only. Nobody you invite can edit your files or re-share ownership; they open the current version and that is it. If you want to share an HTML presentation the same way, the access model is identical - it is per artifact, not per file type.

Option B: a revocable, expiring share link

Sometimes asking a reviewer to sign in is too much. For that, create a view link instead. It is still not a permanent public URL:

• It expires. Free-plan links stay live for up to 30 days; you choose the window and can issue a fresh one anytime.
• It is revocable. Kill the link and the door closes, even if someone saved the URL.
• It is not password protected. Be honest with yourself about this: a link is a secret you can expire and revoke, not a vault. For truly sensitive material, use Option A.

Treat the share link as “convenient and temporary,” and the email grant as “private and durable.” Most client work uses both: an email grant for the decision-maker, a short-lived link for a quick look.

Folders: share a set of artifacts with one grant

If you send the same client more than one deck, do not manage access artifact by artifact. Put them in a folder and grant access to the folder. Access inherits down the tree, so a new deck you drop into that folder is already shared with the right person. Remove the grant once and everything under it closes.

This keeps “who can see what” down to a short list you can actually reason about, instead of a pile of individual links.

Let Claude or Cursor set access for you

If you already publish through an agent, access is one more thing it can handle. Model Context Protocol (MCP) lets Claude or Cursor act on your Prezzly account, so you can say: “publish this artifact and give read access to [email protected].” The agent creates the deck and sets the grant in the same step - you never touch a share dialog.

This builds on MCP for presentations: the same connection that lets an agent publish and revise a deck also lets it decide who can open it. Connect once on the Connections page, then let the agent do the busywork.

For teams: named access and SSO on higher plans

The email-grant model scales to a small team without anything fancy: everyone opens what they were granted, under Shared. For larger organizations, higher plans add single sign-on and domain-based access so people get in with their work identity instead of individual invites. If you are a solo consultant, you will likely never need that - Option A already covers “only these people.”

Whatever the plan, the principle holds: you decide who opens the artifact, and you can change your mind later.

Frequently Asked Questions (FAQ)

Can I make a Claude artifact link private so only certain people open it?

Yes. Host the artifact, then grant read access to specific email addresses. Those people sign in and see it under Shared. There is no public link in that flow, so it is not open to “anyone with the URL.”

Can I password protect the link?

No. Links are not password protected. What you get instead is a link that expires and can be revoked, plus email-based access for anything that should stay private. For sensitive material, use the email grant rather than a link.

Can I see who opened my artifact?

No. Prezzly does not provide viewer analytics or per-person open tracking. Control is on the access side (who can open it), not on the reporting side.

How do I take back access after I have shared it?

Remove the email grant, or revoke the share link. Either one closes the door, including for someone who saved the URL earlier.

Can I share several decks with one client at once?

Yes. Put them in a folder and grant access to the folder. Access inherits to everything inside, and new decks you add later are covered automatically.

---

Host your Claude artifact once, then decide who gets in. Share it privately with an email grant, or send a link you can expire and revoke - your call, not the whole internet’s.