How to share Claude Code artifacts outside your organization
Claude Code artifacts are private by default and, on Team and Enterprise, can only reach people outside your organization through a public link that an Owner has to enable first. That link has no password, no expiry and no record of who opened it. To send a Claude Code report or prototype to a client, keep the HTML file and publish it to Outbox from the same session: you get one private link per person, an optional passphrase, an expiry and an email when they open it.
How Claude Code sharing works
When Claude Code publishes an artifact, it lands at a private claude.ai URL that only you can see. From the Share control you can grant access to specific people or everyone in your organization (Team and Enterprise), or create a public link anyone on the internet can open.
On Pro and Max, the choice is private or public. On Team and Enterprise, public sharing is off until an Owner turns on External sharing for the whole organization. That's a deliberate policy decision, and many companies leave it off.
What an outside viewer gets
Even when public links are allowed, the experience for a client is limited by design. Someone who opens a public link without signing in, or from outside your organization, sees the label "Content is user-generated and unverified." instead of your name. They can't see or add comments. Sections that call connectors don't run for them. And there's no password, expiry or open tracking on the link.
Sessions that can't publish artifacts at all
Artifacts require a session signed in with a claude.ai account on the Anthropic API. According to the Claude Code docs, sessions using an API key, an LLM gateway token or a cloud-provider credential can't publish; neither can Claude Code on Amazon Bedrock, Google Cloud or Microsoft Foundry, organizations with Zero Data Retention, HIPAA or customer-managed keys, or runs with -p and the Agent SDK by default.
Outbox doesn't depend on any of that: it's an HTTP API with its own key, so the same workflow works from any session, model provider or CI job.
Claude Code artifact vs Outbox for client delivery
| Claude Code artifact | Outbox | |
|---|---|---|
| Reach people outside your org | Public link, if an Owner allows it | Private per-person links on every plan |
| Viewer needs an account | Depends on artifact type; see the Help Center | No |
| Password and expiry | Not described in the docs | Optional passphrase; expiry from 1 to 365 days |
| Know who opened it | Not described in the docs | Opens recorded per recipient, with an email alert |
| Your name on the page | Replaced by an "unverified" label for outside viewers | Your name and logo on the passphrase screen and the shared page |
| Update after sending | Republish to the same URL | Republish to the same slug; the links keep working |
| Works with API-key or Bedrock sessions | No | Yes |
| Page size | Up to 16 MiB rendered | Up to 10 MB per page on Free, 25 MB on paid plans |
Step by step from Claude Code
Unless you name a location, Claude Code writes the artifact to a temporary folder outside your project. Ask for a real file first, then publish it.
claude mcp add outbox --env OUTBOX_API_KEY=outbox_xxxxxxxx -- npx -y @out-box/mcp
- Ask: "Save this report as reports/acme-audit.html in the project."
- Connect Outbox once, with the local MCP server below or the skill (npx skills add jonathanleiva15/out-box-skills).
- Ask: "Publish reports/acme-audit.html to Outbox as clients/acme/audit." It's private until you share it.
- Ask: "Create a share link for Dana at Acme, expiring in 30 days, with a passphrase."
- Send Dana the link, and the passphrase separately. You'll get an email when she opens it.
Keep iterating after you send
Client feedback rarely ends at version one. When Claude republishes to the same slug, Dana's link keeps working and shows the new version; Outbox keeps the previous ones (the last 15) so you can diff or roll back. If the engagement ends, revoke the link and it stops working immediately while the page stays in your library.
For teams, Outbox's Team plan puts every rep's agent in one company space with per-client folders and a shared view of who opened what, for $49 a month for the whole company (up to 10 publishers, early access).
Comparisons
Frequently asked questions
Can I share a Claude Code artifact with a client on a Team plan?
Only through a public link, and only if an Owner has turned on External sharing for the organization. Otherwise, access is limited to members.
Will my client see my name on a public Claude Code artifact?
Not if they aren't signed in to your organization: the docs say they see "Content is user-generated and unverified." instead.
My Claude Code session uses an API key. Can I still share HTML?
Not as a Claude artifact: API-key sessions can't publish them. You can publish the HTML to Outbox from the same session with an Outbox API key.
Is the Outbox link private?
The page stays private in your library; only people with a share link (and the passphrase, if you set one) can open it, and only until it expires or you revoke it.
Related guides
Sources
Updated 2026-10-11.