Claude Teams artifact workaround: share any artifact

2026-05-24·9 min readclaudeartifactsworkflow

By Sankalp Agarwal · Founder, Anchorify

Claude Teams plan disables public artifact sharing by default. If you upgraded from Claude Pro and noticed the "Share" button no longer generates a public link, this is why. There is a fix that takes under two minutes for any artifact type. This post is the cookbook: the exact steps for markdown artifacts, React and interactive artifacts, code artifacts, and CSV data, plus a walkthrough of what your client or colleague actually sees when they open the result.

If you want the background on why Anthropic made this change and how it compares to the Pro plan, the sister post covers that overview. This post assumes you already know you have the problem and want the fix.

Why Claude Teams removed public artifact sharing by default

Claude Teams disables public artifact sharing because enterprise workspace admins need control over what leaves the organisation. This is a data-governance default, not a product downgrade.

The Teams plan ($25/seat/month) is designed for multi-seat workspaces, often under company IT policy. Public artifact sharing means any team member can create a URL that anyone on the internet can open. Enterprise admins routinely turn that off on day one, so Anthropic made "off" the default. Workspace admins can re-enable it in their settings, but if your admin hasn't done that, you're effectively blocked.

Claude Pro ($20/month, individual plan) is unaffected. Pro users still see the "Share" button in the artifact pane and still get a public claude.ai/artifacts/<id> URL that a client can open in any browser without a Claude account.

The workaround below restores the outcome Pro users have (a public URL your client can open without a login) using a different path.

The exact workflow for markdown artifacts

Markdown artifacts are the easiest to share: copy the text, paste it into a .md file, and publish it as a URL with one command.

Step 1. In the Claude artifact pane, click the copy icon (top-right of the artifact). This copies the raw markdown text.

Step 2. Open any text editor or terminal and paste into a new file:

# In your terminal or editor
pbpaste > deliverable.md     # macOS: paste clipboard to file
# Or open VS Code, paste, and save as deliverable.md

Step 3. Publish it:

anchorify deliverable.md
# → https://anchorify.io/your-org/your-project/deliverable

The URL comes back in stdout. Send it to your client. They click it and the document opens in their browser: tables, headings, and code blocks rendered cleanly, no login required, no "request access" gate.

Updating later: Re-run the same command after you edit the file. The URL stays the same; the content updates.

# Next week, after changes:
anchorify deliverable.md
# Same URL, updated content

If you want to control visibility, use --public (anyone with the URL can read it) or --members (only your Anchorify org members):

anchorify deliverable.md --public

The full CLI reference is in the docs.

The exact workflow for React and interactive artifacts

React and interactive artifacts need one extra step before you copy: ask Claude to produce the self-contained HTML version.

Claude renders React artifacts in a sandboxed iframe using its own runtime. When you copy from the artifact pane, you get the JSX source, not a runnable page. The fix is to ask Claude to output the whole thing as a standalone HTML file with inline scripts.

Step 1. In the same Claude conversation, send this message:

Give me the full self-contained HTML version of this artifact.
Inline all scripts and styles so it runs in a browser without
any external dependencies.

Claude will output an HTML artifact with everything bundled. If it uses a CDN (e.g., React from unpkg), that's fine: the page still loads standalone as long as the client has internet access.

Step 2. Copy the HTML from the new artifact. Paste into a file:

pbpaste > tool.html

Step 3. Publish with the HTML type flag:

anchorify tool.html --type html
# → https://anchorify.io/your-org/your-project/tool

The client opens the URL and the page renders in their browser as a normal HTML page. For display-oriented artifacts (dashboards, calculators, charts) this works reliably. For complex React component trees that depend on a build system or private npm packages, results vary; ask Claude to simplify the dependency surface if the page doesn't load.

The exact workflow for code artifacts

Code artifacts (Python scripts, SQL queries, TypeScript files, shell scripts) publish directly with syntax highlighting.

Step 1. Copy the code from the artifact pane.

Step 2. Paste into a file with the right extension:

pbpaste > analysis.py
# or: analysis.sql, transform.ts, setup.sh

Step 3. Publish:

anchorify analysis.py
# → https://anchorify.io/your-org/your-project/analysis

The recipient sees syntax-highlighted code in a clean reader view. Useful when you're handing a script to a developer on the client's team who doesn't have Claude access but needs to review or run what Claude wrote.

The exact workflow for CSV and data artifacts

CSV artifacts from Claude publish as sortable, searchable tables that any non-technical recipient can read in a browser without a spreadsheet app.

Step 1. Copy the CSV content from the artifact pane (Claude formats CSVs as code blocks or as a file).

Step 2. Paste into a .csv file:

pbpaste > data-export.csv

Step 3. Publish:

anchorify data-export.csv
# → https://anchorify.io/your-org/your-project/data-export

The client sees a table they can sort by column. Useful for sharing data pulls, keyword lists, or structured research outputs with a non-technical recipient who would otherwise ask you to paste it into a Google Sheet.

The artifact type comparison at a glance

What clients actually see when they open the link

The recipient gets a clean URL that opens immediately in any browser without a login prompt, a permission request, or a "request access" gate.

There is no "sign in to view" screen. No "you need a Google account" prompt. No Notion-style "this page is private" wall. The URL is public (or unlisted, if you set --members or use a password) and loads in under a second.

On a markdown document, the client sees formatting that looks like a finished document: headings are styled, tables are clean, code blocks have a monospace font and scroll on mobile. It is not a code dump. Compared to pasting into a Google Doc, the share step is one command and zero permission decisions.

If you enabled comments, the client can leave inline or document-level feedback without signing up. They can comment as a guest. If you re-run the command next week with updated content, the client's bookmark still resolves to the latest version. The URL does not change.

For sensitive deliverables, set visibility to unlisted (the default) so only people with the exact URL can read it, or add a password:

anchorify deliverable.md --unlisted    # default
anchorify deliverable.md --public      # indexed and discoverable

Full visibility options are in the getting-started guide.

Frequently Asked Questions

The most common questions from Claude Teams users trying to share artifacts with clients who do not have Claude accounts.

Can my Claude Teams admin re-enable artifact sharing?

Yes. A workspace admin on Claude Teams can enable public artifact sharing in the workspace settings. If your admin has done this, the native Claude "Share" button will work again and you don't need this workaround. If they haven't, or if you need sharing to work today without waiting for an admin change, the workflow above is the direct path.

Does this workaround cost anything?

Anchorify is free during the current beta. You sign in with Google to publish, and there is no paywall on the read side. Clients who open your shared URL pay nothing and need no account. Sign up at anchorify.io.

What happens if I update the artifact in Claude?

The Anchorify URL is tied to the local file you published, not to Claude's version of the artifact. If you iterate on the artifact in Claude and want the URL to reflect the new version, copy the updated artifact content, update your local file, and re-run anchorify yourfile.md. The URL stays put; the content updates in place. This is different from native Claude artifact sharing, where each new share generates a new URL.

Can I share a Claude artifact that contains sensitive client data?

Use unlisted visibility (the default) so only someone with the exact URL can read the page. Anchorify does not index unlisted shares in any public directory. For an additional layer, set a password: anchorify file.md --password "your-password". The recipient gets a password prompt before the content loads. For highly sensitive data, check your organisation's policy on third-party document hosting before publishing.

Does the recipient need to create an Anchorify account to view the document?

No. Anchorify has no "sign in to view" gate on the reader side. The recipient opens the URL and the document loads. No account, no extension, no app download. Publishing requires a Google sign-in; reading requires nothing.

Sources

• Claude pricing: Pro vs Teams plan comparison. Plan feature tables, per-seat pricing, and sharing capabilities by plan tier.
• Anthropic Claude for Teams product page. Canonical Teams plan description including admin controls and workspace features.
• Anchorify CLI documentation. Command shapes for anchorify, --type, --public, --members, --password flags.

Anchorify turns any file (including anything Claude generates) into a shareable URL with one command. Free during beta, no paywall on the read side. Sign in at anchorify.io.

Last updated: 2026-05-24