--- title: How to Make a Claude Artifact Private (Company-Only) slug: /blog/make-claude-artifact-private publishedAt: "2026-07-27" updatedAt: "2026-07-27" priority: P0 keyword: make claude artifact private secondary_keywords: how to make claude artifact private, claude artifact private link, claude artifact company only, keep claude artifact private word_count_target: 1500 funnel_stage: Awareness → Activation schema: FAQPage, HowTo, Article description: "Claude's publish button makes an artifact public. To make it private to your company, publish it behind Google or Microsoft SSO so only your email domain can open it, with no Claude seat required." --- # How to Make a Claude Artifact Private (Company-Only) > **TL;DR:** Claude's publish button makes an artifact public, and sharing inside a Claude org requires every viewer to hold a Claude seat. To make an artifact private to your company only, publish it to display.dev behind your Google or Microsoft SSO. Only people on your email domain can open it, no Claude subscription needed, and updates land on the same URL. --- ## Why the Claude publish button doesn't make it private When you press publish inside Claude, the artifact becomes a page anyone with the link can open, with no sign-in. That is public, not private. Sharing through a Claude Team or Enterprise organization is more restricted, but it gates on Claude subscriptions: every viewer needs a paid Claude seat in your org to open the page. Neither setting gives you the option internal work needs, which is a page only your company can open, using the accounts your company already has. For the full breakdown of what "private" means at each stage, see [are Claude artifacts private](/blog/are-claude-artifacts-private). To get a genuinely company-only link, you publish the artifact somewhere that gates on your company identity. That is what the steps below do. --- ## Make a Claude artifact private in four steps The fastest path uses display.dev's MCP connector, so you never leave the Claude conversation. Total setup is about five minutes the first time, then seconds per artifact after that. **Step 1: Connect display.dev to Claude.** In display.dev, go to Settings and create an API key. In Claude Desktop, open Settings, add display.dev as a custom MCP connector using `https://api.display.dev/v1/mcp`, and sign in when the browser tab opens. No config file to edit. If your IT team manages devices, they can push this connector to everyone once. **Step 2: Ask Claude to publish it privately.** In the conversation with your artifact, say "publish this to my team" or "create a link only my company can open." Claude calls the publish tool and returns a display.dev URL in the chat. The artifact is stored independently of Claude from this point on. **Step 3: Set the artifact to company-only.** Choose who can open the link: everyone at your company behind Google or Microsoft SSO, a list of specific invited email addresses, or public. For a company-only artifact, keep it gated to your organization so only people on your verified email domain get in. You can change this per artifact at any time. **Step 4: Share the URL.** Paste the link into Slack, email, a doc, wherever. When a colleague clicks it, they sign in once with their work Google or Microsoft account and see the full interactive page. Nobody buys a Claude seat, and the content never sat at a public address. Prefer to work from a file? In Claude Code the artifact is already on disk, so run `dsp publish ./report.html` and you get the same company-gated URL back in about 15 seconds. The [share a Claude artifact](/share-claude-artifact) page has the full walkthrough for both paths. --- ## What "private" looks like for each option | Setting | Who can open it | Claude seat required | Company-only | | ---------------------------- | ----------------------------- | -------------------- | -------------------------- | | Claude publish (public) | Anyone with the link | No | ❌ | | Claude org share | Teammates in your Claude org | Yes | Partly (Claude-seat-gated) | | display.dev – invited emails | Specific addresses you add | No | Scoped to those people | | display.dev – company SSO | Everyone on your email domain | No | ✅ | | display.dev – public | Anyone with the link | No | ❌ (by choice) | The row internal work usually wants is company SSO: open to every colleague, closed to everyone else, and no per-seat cost. This access model is called gated publishing; the concept is explained in [what is gated publishing](/blog/what-is-gated-publishing). --- ## Why company SSO beats an obscure link A common workaround is to publish publicly and rely on the URL being long and hard to guess. That is not privacy. The page is genuinely on the open web, so it can be forwarded, cached, or indexed, and you get no record of who opened it. Company SSO is different in kind. Access is tied to identity, not to knowledge of a secret address. If someone forwards the link to a person outside your company, that person hits a sign-in wall and cannot get in. And because each viewer authenticates as themselves, Pro and Enterprise plans keep an audit trail of who viewed which version, for 90 to 365 days. There is also a cost angle that only shows up at scale. Viewers outnumber creators by roughly ten to one. Gating on Claude seats charges for each of those viewers. Gating on company SSO charges for none of them: display.dev has no per-seat fee at any tier, and viewers are unlimited. --- ## FAQ **How do I make a Claude artifact private instead of public?** Don't use Claude's public publish button for internal work. Instead publish the artifact to display.dev and set its visibility to your company, so only people on your Google or Microsoft email domain can open it. From Claude Desktop, connect the MCP server and say "publish this to my team." From Claude Code, run `dsp publish ./file.html`. **Can I make a Claude artifact private without a paid Claude plan for my whole team?** Yes, and that is the main reason to publish outside Claude. Claude's own org sharing requires each viewer to hold a Claude seat. When you publish to display.dev, viewers sign in with the Google or Microsoft account they already use for work, so no colleague needs a Claude subscription to read the page. **Can I restrict a Claude artifact to specific people rather than the whole company?** Yes. On display.dev, alongside company-wide SSO you can add a list of specific email addresses, including people at a client or partner company. They get one-time password access to that artifact without being added to your organization. **If I make it private, can I still update the artifact later?** Yes. Publishing again with the artifact's `short_id` and current `base_version` replaces the content at the same URL and keeps the version history. Your agent can do this after reading a teammate's inline comment, then resolve the thread. **Does making a Claude artifact private stop working if I cancel Claude?** No. Once published to display.dev, the artifact is stored independently of Claude. Ending your Claude subscription, closing the conversation, or switching agents does not affect it, and the URL keeps working. Details in [who can see a Claude artifact link](/blog/who-can-see-claude-artifact-link).