Skip to content

How to share a Claude artifact with your colleagues, even without a Claude account (2026)

Claude just built you a useful artifact: a calculator, a schedule, a small form. To make it serve the whole team, there are two paths, and the right one depends on your colleagues: do they all have a Claude account, or does it need to be shared without one.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.

View as Markdown

Sharing a Claude artifact with colleagues who have no Claude account: the artifact leaves the conversation and becomes a tool shared on while, which the team opens in their browser

An artifact is the page Claude builds in the conversation: a quote calculator, a team schedule, a small request form. It is often good enough to serve everyone, and that is when the question comes up: how do you share it with your colleagues, especially if they do not all have a Claude account?

The short version. To show an artifact once, Claude’s public link is enough. To make it the team’s tool, restricted to your colleagues or open to a client with a password, ask Claude to put it on while: your colleagues use it with no Claude account.

The two ways to share an artifact

Claude’s sharingwhile
For whomShowing an artifact, quicklyMaking it the team’s tool
Your colleaguesA Claude account in the organization, for restricted sharingNo Claude account
A clientA public link, with no passwordAn access link and a password, valid for 1, 7 or 30 days
The dataUp to 100 MB per artifact, read-only outside the organizationKept, and backed up every day

Claude’s sharing: fast, but with an account

An artifact starts private, and you share it in one click1. On every plan, a public link makes it available to anyone who has it, and most artifacts shared that way open without signing in to Claude. It is perfect for showing a prototype.

On paid plans, an artifact can also keep data, up to 100 MB, private to each person or shared by everyone3. Someone outside your organization can read it after signing in to Claude, but cannot change it1. So a client cannot fill in their part there.

On Team and Enterprise plans, you can also share it with the whole organization or with specific people, who then need a Claude account in the organization. The public link stays off there until an owner allows external sharing1. In other words, for a tool restricted to the team, each colleague needs their own account.

Putting the artifact on while, in three steps

With while, Claude puts the artifact on while itself, from the conversation, and it becomes a tool with its own address.

Sharing a Claude artifact: a public link open to anyone, or a tool on while restricted to colleagues without a Claude account, with a client getting in by link and password
The public link shows the artifact; while makes it the team's tool.
  1. Add the while connector to Claude. On Pro or Max, open Customize, then Connectors, and add a custom connector at https://app.while.sh/mcp. On Team or Enterprise, an owner adds it for the organization, then each person connects to it. Claude’s free plan allows one2.
  2. Ask Claude to put the artifact on while. Without a while account, it does so as a free trial, and gives you a link to keep it.
  3. Choose who uses it. Once the tool is kept in your account, you restrict it to your colleagues, open it to a client, or to everyone.

You, to your AI: Put this artifact on while, and restrict it to the team.

Choosing who uses the artifact

This is where while changes things for a team tool. You choose who uses it, and nobody needs a Claude account:

  • Only your colleagues. They sign in with a while account, up to 3 people on the Free plan, or with their email account, Google or Microsoft, on the Pro plan. See restricting a tool to your colleagues.
  • A client or a supplier. They use the tool with an access link and a password, valid for 1, 7 or 30 days, without creating an account.
  • Everyone. A person on your team approves opening it first.

Going further with your artifact

An artifact on while becomes a real tool, and you improve it by asking Claude:

  • Keep the team’s data. Ask Claude to keep the answers: it adds what is needed to store them, and while backs them up every day.
  • Give it your own address, like schedule.your-company.com: Claude declares it, and you add the records it gives you at your domain provider.
  • Go back to the previous version if a change disappoints: within 30 minutes of an update it is immediate, then a few seconds after that.

The credentials for your other software stay in while, and Claude never sees them. Your tools are hosted in France by Nextmap. To compare with ChatGPT Sites and Cursor Apps, read our comparison of ways to share a tool built with AI, and if you are weighing the Team plan, our Claude Team or while math.

Try it on your artifact

To try it, give this message to Claude. The trial is free, with no sign-up, and your artifact has its address in 3 minutes.

The message to give your AI
Read while.sh/agents and help me get started with while.

In the docs: Versions and rollback.

Sources

  1. Anthropic, Share artifacts, accessed November 18, 2026
  2. Anthropic, Get started with custom connectors using remote MCP, accessed November 18, 2026
  3. Anthropic, What are artifacts and how do I use them?, accessed November 18, 2026

Questions

Do my colleagues need a Claude account to open an artifact?

For a public link, no: most artifacts shared that way open without signing in. For sharing restricted to the organization, yes1. On while, they use it with no Claude account.

Does the while connector work with Claude’s free plan?

Yes. Custom connectors exist on every Claude plan, and the free plan allows one2.

Can an artifact on while keep data?

Yes. Ask Claude to keep the team’s answers: it adds what is needed to store them, and while backs them up every day.

How do I update the artifact?

Ask Claude for the change, in the conversation. It makes it and puts it back on while, at the same address.

What about an artifact built with ChatGPT or Gemini?

The same path works with any AI that connects to while, ChatGPT included.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh