How to Share Claude Code Artifacts With Your Whole Team

The problem with Claude Code artifact sharing

Claude Code Artifacts can turn session work into a private page on claude.ai. Publishing is available on Pro, Max, Team, and Enterprise plans — but sharing isn't: on Pro and Max the page stays private to you alone, and it's only on Team and Enterprise that you can share it, and even then only inside your Claude org. The page is viewable only by Claude seats in that org, the source has to be Claude, and there's no external or public sharing and no comments. After generating an architecture diagram, a visual report, or an interactive presentation, you can publish it, but the moment you want a viewer who isn't in your Claude org — or you're on Pro or Max and want to share it at all — they're locked out.

The claude.ai web UI also has a Publish button, but:

1. It creates a fully public URL with no company restriction.
2. Claude Code Artifacts and Claude web artifacts are different surfaces, and both keep viewing bound to Claude.

The result: every Claude Code session that produces an HTML artifact for a cross-functional audience runs into the same wall. You build something great, you need anyone with a company login to open it, and Claude's own surfaces only reach people who hold Claude seats.

Here are all your options, honest about what works and what doesn't.

Option 1 – Screenshot

How it works: Take a screenshot of the rendered HTML page and share the image in Slack.

Who it works for: Sharing a quick visual when interactivity doesn't matter (a static mockup, a color palette, a basic diagram).

Who it doesn't work for: Anyone sharing interactive content. Charts, sortable tables, animated diagrams, tabs, and collapsible sections all disappear. The screenshot is a JPEG of an application; it looks like you shared something, but you didn't.

Verdict: Don't, unless the artifact is purely decorative and you're certain the static version is sufficient. Even then, you lose the ability to update and re-share via the same URL.

Option 2 – Share via Claude Team/Enterprise

How it works: Claude Code Artifacts publishes session work as private interactive pages with live updates and versions. Publishing works on Pro, Max, Team, and Enterprise, but sharing is Team/Enterprise-only — on Pro and Max the page can't be shared with anyone. On Team or Enterprise, members of your Claude organization click the link and view the artifact inside Claude.

Who it works for: Teams where every person who needs to view the artifact has a Claude Team or Enterprise seat.

Who it doesn't work for: Anyone sharing with PMs, VPs, legal, sales, or designers who don't have Claude seats. At $25–$30/seat/month, adding 20 non-technical stakeholders as viewers costs $500–$600/month in new seats for people who only need to view content, not use Claude.

Additional constraints: Claude-only as a source (a Cursor, Codex, or CI artifact can't publish here), no external or public sharing, and no comments. Feedback has to happen somewhere other than the page.

Verdict: Works for engineering-only audiences on Claude Team, but fails for cross-functional sharing, for any non-Claude agent's output, and for any viewer who isn't in your Claude org.

Option 3 – GitHub Pages

How it works: Push the HTML file to a gh-pages branch in a GitHub repo, configure GitHub Pages for that repo, and get a public or private URL.

Who it works for:

• Public repos: anyone can view, no auth required. Fine for open source output.
• Private repos: viewers need GitHub accounts + your team needs GitHub Enterprise Cloud.

Who it doesn't work for: Any non-engineer stakeholder. Your PM and your VP of Sales don't have GitHub accounts. Getting them on GitHub and configured for private repo access requires an Enterprise Cloud seat at $21/user/month per viewer, which is $2,100/month for 100 viewers.

Setup time: 5–30 minutes for the first artifact, depending on whether the repo and Pages config already exist.

Verdict: Engineering-only audiences on public repos or Enterprise Cloud; not useful for cross-functional sharing.

Option 4 – Deploy to Vercel or Netlify

How it works: Create a project, connect a git repository, push your HTML, and deploy.

Important constraint: Vercel and Netlify require a git-connected project structure. You cannot upload a single HTML file. Every artifact needs its own repo or a specific folder in a shared repo, creating overhead that doesn't exist in the "one file" publish model.

Costs for auth:

• Vercel password protection: $150/month add-on on Pro. Shared password, not identity-aware.
• Vercel SSO: $300/month add-on on Pro. Identity-aware, but $300/month per project.
• Netlify SSO: Enterprise-only.

Who it works for: Teams already using Vercel for app deployment, wanting basic password protection on preview deployments they've already built.

Who it doesn't work for: Teams trying to publish ad-hoc HTML files without building a deployment pipeline, teams who want SSO without Enterprise pricing, and non-technical publishers.

Verdict: Overkill for publishing HTML files; appropriate for application deployment with auth bolted on.

Option 5 – Gated publishing with display.dev ✓ (recommended)

This is the direct solution to the problem.

Install once:

npm install -g @displaydev/cli

Authenticate once:

dsp login

Publish every time (15 seconds):

dsp publish ./output.html

Paste that URL in Slack, Notion, Jira, or email. Your teammates click it, authenticate with their company Google or Microsoft email once (five seconds), and see the full interactive artifact: charts, animations, tabs, everything exactly as you built it.

No accounts for viewers to create, no GitHub, no enterprise contract, no IT ticket.

For non-technical teammates (PMs, analysts, executives):

Configure Claude Desktop MCP once. After that, in any Claude conversation, they say: "Publish this to my team." Claude calls the display.dev MCP tool, gets back a company-gated URL, and returns it in the conversation. No terminal, file system, or configuration after initial setup.

Cost:

• Free tier: one-time password authentication. Viewers receive a one-time login link via email. Works fine for occasional sharing.
• Pro (€49/month): Google Workspace and Microsoft 365 SSO. One click, no email check needed.

After you publish: comments and who viewed

Publishing isn't the end of the loop. Two things happen at the gated URL that a public link or a screenshot can't do:

• Inline comments. A teammate pins a comment to the exact spot in the artifact they're questioning. You (or Claude Code itself, reading the comments back over MCP) fetch the current version, republish with the artifact ID and base version, and resolve the thread. Feedback lands on the work, with context, not in a Slack thread that scrolls away.
• Who viewed it. Because viewers sign in with their company identity, the view record shows which people opened the artifact and when, by verified name, not an anonymous count. (How to know who opened your link.)

That turns a one-way share into the agent's feedback loop: publish, collect comments, fetch the current version, republish with the artifact ID and base version, then resolve the thread.

The comparison

Setting up display.dev for your team (5 minutes)

Step 1: Install the CLI

npm install -g @displaydev/cli

Step 2: Create your organization Go to display.dev, create an account, and set your company domain (e.g., acme.com). Anyone authenticating with an @acme.com email gets access.

Step 3: Authenticate the CLI

dsp login

Step 4: Publish your first artifact

dsp publish ./your-artifact.html

Step 5: Share the URL Paste it anywhere; the URL is permanent and works forever.

For the team: Share your organization invite link. Teammates install the CLI, run dsp login, and can publish immediately. The whole team shares one organization and one billing seat.

For MCP (non-technical users): See the MCP setup guide for Claude Desktop configuration.