Shared AI Workspaces or a Separately Hosted Website?

Claude artifacts (pages and apps that Claude makes in a chat) and other AI workspaces now turn a session into a working page. The page can be a dashboard, a walkthrough, a checklist, a visual report or a small app. Inside a team, that is often all you need. The question comes later, when people outside the workspace must open the page: a client, an investor, a partner or the public.

This guide explains what the sharing in Claude does on Team and Enterprise plans, and when that is enough. It also shows how to move a page to a separately hosted site when it is not enough.

What sharing inside Claude covers

On Team and Enterprise plans, you share an artifact through your organization:

• Open the artifact and select Share. Under Who has access, choose Anyone at your organization. Only people who are signed in to your organization can open it.
• You can add people from your organization by name or email. Give each person Can view, Commenter or Can edit access. On Enterprise plans, you can also add groups.
• The Anyone with the link option appears only if an Owner turns on External sharing in Organization settings > Artifacts. An Owner can also allow it for one artifact only.
• Recipients need a Claude account. There is one exception. Anyone with the link can open an older chat artifact that a user published from a Free, Pro or Max plan.
• If you share a chat artifact, viewers also get access to the attachments and files in that chat. Before you share, make sure that you want viewers to see those files.

On Free, Pro and Max plans, Publish makes a public link. Anyone can open that link without a Claude account. On Pro and Max, newer artifacts use Share instead, with the options Only you or Anyone with the link. Unpublish removes access permanently, and you cannot publish that artifact again later.

When to keep the page in the workspace

Keep the page in Claude when:

• Everyone who needs the page already has access to the same organization.
• The page belongs to the working session and its context.
• The audience is internal.
• The page still changes quickly.
• You want comments and edits to stay attached to the artifact.

When to host it separately

Move the page to its own website when:

• You do not want readers outside the organization to need a Claude account.
• Your organization keeps external sharing off, but a client must still see the page.
• You want your own domain, or a stable URL that lasts longer than the session.
• You need an access rule that the workspace does not have, for example a list of approved email addresses outside the company.
• You want analytics or a log of sign-ins.
• You want several tools (Claude, ChatGPT, Codex or a script) to update the same files.

Check what needs to move

1. Get the code. For an older chat artifact, use the controls at the top of the artifact panel. With them, you can view, copy or download the code. For an artifact made from a template, use Export. Documents export to Word, PDF, Markdown and Google Docs.

2. Find the parts that depend on Claude. AI-powered artifacts run on Anthropic’s infrastructure, and they ask users to sign in with their Claude account. Artifact storage and connected apps are also Claude features. A copied HTML file does not bring these services with it. If the page calls a model, your copy needs its own backend (a server program) that holds an API key. Never put the key in browser code.

3. Test the copy outside Claude. Save the files in a folder, with index.html at the top level. Then serve the folder locally:

   python3 -m http.server 8000

   Open http://localhost:8000 and click through every part of the page. Look in the browser console for errors and failed requests.

Publish the copy and choose access

Audience	Host and setting
Anyone	Cloudflare Pages, GitHub Pages or Netlify with no gate
Named people outside the company	Cloudflare Pages with Cloudflare Access. Visitors get a one-time code by email. You allow addresses with Emails, or a domain with Emails ending in
A small group that shares one password	Netlify password protection (Pro plan or higher) or Vercel Password Protection (Pro as a paid add-on, or Enterprise)
People who already have Vercel accounts	Vercel Authentication, which works on every plan

GitHub Pages has no access control. Its sites are public even when the repository is private.

The fastest way to get a live copy is a Cloudflare Pages direct upload. In the dashboard, go to Workers & Pages. Select Create application. Choose the drag-and-drop upload. Give the project a name, and then drop the folder. In a terminal, log in with npx wrangler login. Create the project with npx wrangler pages project create. Then deploy the folder:

npx wrangler pages deploy my-artifact

The site goes live at <project>.pages.dev. To add your own domain, use the Custom domains tab of the project. On Cloudflare, an Access login needs a separate Access application for the production address and for each custom domain. The Pages known issues page lists the steps.

Let several tools update the same site

A separately hosted site is a set of files, so any tool that can edit files can update it:

• Claude writes the first version of a report.
• ChatGPT rewrites the summary.
• Codex fixes the layout.
• A script refreshes the data every morning.

Keep the files in a Git repository. Connect the repository to the host, so that every push deploys to the same URL. On Cloudflare Pages, connect the repository when you create the project. A Direct Upload project cannot change to Git later. Each tool commits to the repository, and readers keep the link that they already have.

Switch over carefully

Keep the original artifact until the hosted copy works for a real reader. Send the new link to one person outside your organization. Make sure that this person can open the page with the access rule that you set. If people must no longer reach the artifact, unshare or unpublish it. If the artifact was public before, use the public artifact search guide to find out whether search engines found it.

A docs portal with Ask AI
and support tickets

Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.

• Publishes from GitHub on every push
• Works with Mintlify repositories
• API console from your OpenAPI file
• MCP server and llms.txt for AI agents
• Ask AI and support tickets
• Analytics for people and AI agents

Start Free→ Questions? Ask AI in our docs

No card required.