# How to share Claude Code artifacts outside your organization

> Claude Code artifacts stay inside your org unless an Owner enables public links. How to send that HTML to a client with a private per-person link instead.

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

## 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
```

## 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

- [Outbox vs Claude Artifacts](https://out-box.dev/en/guides/vs/claude-artifacts)
- [Outbox vs Derive](https://out-box.dev/en/guides/vs/derive)
- [Outbox vs Display.dev](https://out-box.dev/en/guides/vs/display-dev)

---

Updated 2026-10-11. HTML version: https://out-box.dev/en/guides/share-claude-code-artifacts-outside-your-org