Guide
How to share a Claude Code artifact with people outside your Claude organization
Updated 30 October 2026
Claude Code artifacts share with people in your Claude Team or Enterprise organization, by email invitation to people with a Claude account, or by a public link whose visitors can’t comment. To show a page to a client, a contractor or a colleague without a Claude seat, and collect their comments, publish the same HTML or Markdown file to ashare.net. They open the link with a code sent to their email; Claude Code reads their comments over MCP, fixes the page and resolves the threads.
What Claude Code artifacts share today
Per Claude Code’s docs, an artifact is a page Claude Code publishes to a private URL on claude.ai. Artifacts need a Pro, Max, Team or Enterprise plan and a session signed in with /login. You share one from the page header:
- Within your organization, on Team and Enterprise: specific people or everyone. Viewers sign in to claude.ai as members of your organization.
- Publicly: a link anyone opens. On Team and Enterprise it stays off until an Owner turns on external sharing.
Comments come from the people you share with inside your organization. Claude reads the threads, and replies to or resolves the ones someone who can edit the artifact sent to Claude. People whose only access is the public link don’t see comments and can’t add any. Anthropic’s Help Center also lists email invitations (beta), up to 50 outside people per artifact: each invitee needs a Claude account under that address and can’t ask Claude in a comment.
The two pages disagree on one point. The Claude Code docs say a public link opens without a claude.ai sign-in; the Help Center says everyone needs a Claude account except for older chat artifacts published with Publish. Check with a private browser window before you send a public link.
Artifacts are also off by default in claude -p, the Agent SDK, the GitHub Action and MCP-server contexts: the usual setup of a scheduled report or a CI job.
Set up ashare once
$ claude mcp add -s user --transport http ashare https://ashare.net/mcpIn Claude Code run /mcp, pick ashare and Authenticate. You sign in with your email; there is no key to copy. The same server works in claude -p and the Agent SDK with an API key in a header.
The plugin adds a skill that walks Claude through the whole review loop and asks who should see a document before it publishes. It reads a key from ASHARE_API_KEY, created on ashare.net/me/api:
$ export ASHARE_API_KEY=<key>
$ claude plugin marketplace add Magir/ashare-plugin
$ claude plugin install ashare@ashareShare the page
Ask Claude Code:
Publish report.html to ashare and share it with lena@client.ioClaude publishes the file and gives you a link like https://ashare.net/a/Qm7rT2wLx9Ke. A new document is private: only you and the people you name open it. You can also say:
- “for everyone at our company”: anyone who signs in with an email on your company domain;
- “make it public with a password, expiring in 7 days”: anyone with the link and the password, until then;
- “make it public”: anyone with the link. ashare links are unguessable and search engines don’t index them.
Lena opens the link, types her email and the 6-digit code from the letter. She needs no Claude account and installs nothing. Someone you didn’t name can ask for access, and you approve or deny it from the email. For private and company documents you see who opened it and when.
Collect the comments
Lena selects a sentence and writes a comment. You get an email when there is something new. Then ask Claude Code:
Go through the comments on the reportClaude lists the open threads with the quoted text, edits the document, replies in each thread with what it changed and resolves it. Every thread is open to the agent, not only the ones a person sent to it. The fix is a new version at the same link. Lena picks a version in the header and compares it with an older one: added text is green, removed text is struck through.
Claude Code artifacts or ashare.net
| What you need | Claude Code artifacts | ashare.net |
|---|---|---|
| Share inside your Claude organization | Yes, on Team and Enterprise | Yes, by company email domain |
| Share with specific people outside it | Email invites in beta; each needs a Claude account | Up to 100 emails; each gets a code by email |
| Comments from outside readers | Invitees with Commenter access; none from the public link | Anyone who opens it, after an email code |
| Password and expiry per link | A retention period an Owner sets; the docs mention no password | Per document |
Publish from claude -p, Agent SDK, CI | Off by default | MCP with a key, CLI, GitHub Action |
| Publish from Codex, Cursor, ChatGPT | No, Claude only | Any MCP client |
| Several files, images, relative links | One page up to 16 MiB; external images blocked | One page up to 5 MB, or a site of up to 200 files and 25 MB |
| Live data from your connectors | Yes, through each viewer’s connection | No, the page is what the agent published |
| Price | Part of Claude Pro, Max, Team, Enterprise | Free for personal email, 50 MB; Pro $5 a month or $48 a year; Company $30 a month for the domain |
If everyone who reads your artifacts is on the same Claude Team or Enterprise plan, Claude Code artifacts already cover it, live data included. ashare.net is for the cases outside that.
Questions
Does the reader need a Claude account?
No. A code sent to their email is enough, or Google or Microsoft sign-in. Readers never pay.
Will the link change when Claude updates the page?
No. Every update is a new version at the same link. You can hide older versions, so readers see only the current one.
Can I limit how long the link works?
Yes. Ask Claude to “expire it in 7 days” or to set a password. After the date the link shows “Link expired”, and you can extend it.
The page is already a Claude Code artifact. Do I start over?
No. Ask Claude Code to publish the same file to ashare: the source is the same HTML or Markdown. In the same session Claude knows where the file is. From a new session, give Claude the artifact’s URL or attach it with /artifacts, and it pulls the current content.
ashare.net: your agent publishes HTML or Markdown and you choose who opens it: your company, specific emails or a password. Readers comment, the agent fixes the document.
Connect your agent