Blog

How to publish something Claude made in a chat, so your team can open it

Claude made a report, a dashboard or a small tool in a Claude.ai chat, and your team needs to open it. What Claude's own sharing does, and how the Spryloom connector publishes it from the chat, behind sign-in, to the people you name.

Plenty of useful work now ends in a Claude.ai chat. Claude turns a messy export into a one-page summary of last month's support tickets. It builds a dashboard of the quarter's hiring numbers for the HR team. It makes a small rota page for the on-call rotation.

Then it has to reach the people it's for. The support summary is for the support leads, the hiring dashboard for HR and the department heads, the rota for the engineers on call. Usually not for anyone else, because it has customer names, salaries or phone numbers in it.

This article is about getting from the chat to a link those people can open. We make Spryloom, and the second option below is ours, so read that part knowing who wrote it.

What publishing it needs

  1. It lives somewhere other than the chat, at an address that stays the same when you update it.
  2. Only the right people can open it, identified by their own work address, not by a shared link.
  3. They don't need anything special to open it: no account on the tool that made it, no software to install.
  4. You can take it back, from one person or from everyone.

Option 1: Claude's own sharing

Claude can share what it made from the chat. Depending on your plan and your organization's settings, that can be a public link to the artifact, an invitation to named people who have Claude accounts, or sharing with everyone in your organization's Claude account. It's zero setup and it's already where you work. For sharing with colleagues who all use Claude, or for something that is fine to be public, it's often the simplest answer.

Check your plan before sharing anything private: who can open the link, whether viewers need a Claude account, and whether you can remove one person's access. The answers differ by plan, and change.

Downloading the file and sending it is fine for a one-off, but each person then has a copy you can't take back, and every change means sending it again.

Option 2: publish it with the Spryloom connector

Spryloom runs pages and apps for teams behind sign-in. Its hosted connector lets Claude.ai publish straight from the chat.

Claude.ai chat publish_page sign-in The page same address invited not invited the page is sent only after sign-in
Claude sends the page. Spryloom serves it only to people who sign in and are on the list.

Add the connector, once

In Claude.ai, open Settings → Connectors, add a custom connector, and give it this address:

https://app.spryloom.com/mcp

The first time Claude uses it, you connect it:

Enter your emailThe address you work with.
Open the linkSpryloom emails it to you.
Check the codeIt has to match.
ApproveFor your workspace.

If your company's mail runs on a business mail service such as Google Workspace or Microsoft 365, that's your company's workspace. Otherwise it's a personal one.

Ask

Say Taylor runs the support team and has the ticket summary open in the chat. Taylor writes: "Publish this with Spryloom for the support leads." Before publishing, Claude asks who should be able to open it, and Taylor picks invited:

Default

Just you

Right while it's half-finished.

Taylor's pick

People you invite

Named people, by email.

Company

Anyone at your company's domain

Needs a company workspace.

Claude publishes the page with the publish_page tool, which takes one self-contained HTML page, a name, a one-sentence description and the visibility. It checks the status until the page is live, in seconds, and gives Taylor the address.

Then: "Invite alex@yourcompany.com and sam@yourcompany.com." Claude uses the connector's invite tool.

What Alex sees

From Spryloom · To alex@yourcompany.com
Subject taylor@yourcompany.com invited you to Ticket summary

You have been invited to Ticket summary

What it does: A one-page summary of last month's support tickets, for the support leads.

Open Ticket summary

It signs you in as alex@yourcompany.com. It works once, for 7 days; after that, sign in with an emailed link.

The button leads to one press of Continue. No password, no Claude account, nothing to install.

Anyone not invited can ask for a sign-in link, and nothing arrives. The page is never sent to them.

From then on, each change is a sentence in the chat:

The page needs a change→Publish again under the same name: same address, next version
The new version is wrong→"Roll it back"
Sam shouldn't see it any more→"Remove sam@yourcompany.com", effective on his next click

Pages that keep what people enter

A plain page can't save anything. If the on-call rota needs people to swap shifts, it needs to keep records. Through the connector, Claude can also publish a page that saves data: it writes the page and a small manifest, spryloom.yaml, declaring the lists, and sends the files. Every record is stamped with who saved it and when, from their sign-in.

The connector can then read and add to those lists from the chat. Ask "who's on call next week?" and Claude reads the page's records with page_data. Ask "add Jordan for the 14th" and it adds a record with save_page_record, as you. It sees only what you would see in the page, and it can change only records you saved yourself. How to make a checklist your whole team can use, without building an app shows a page like this in use.

What it doesn't do

  • It can't see your computer. Claude.ai publishes what's in the conversation: one page, or the files it wrote. A folder on your machine, a zip, or a GitHub repository needs the command line (npx -y spryloom publish) or the Spryloom tools in a coding agent.
  • A single page is up to 512 KB of HTML, with its styles and scripts inside it. Images have to be small enough to fit inline. Larger work is sent as files, up to 300 files and 3 MB through the connector. Anything bigger needs the command line.
  • A page's scripts can talk only to the page. It can't call an outside API from the browser. Scripts may load from cdnjs, jsDelivr and unpkg, styles from cdnjs, jsDelivr and Google Fonts, and fonts from Google Fonts, cdnjs and jsDelivr.
  • Secrets don't go through the chat. If a tool needs an API key, it becomes an app, and the key is set from a terminal with spry secrets.
  • Pages in your connected workspace only. The connector reads and writes pages in the workspace you approved it for.
  • Everyone signs in. It isn't a way to publish something for the open web.

If the work started as a Claude artifact your team already relies on, with saved data, Claude Code can bring it across as a page that saves data, records included. The Spryloom skill has the steps.

Start here

In Claude.ai, add the connector https://app.spryloom.com/mcp under Settings → Connectors, then say "publish this with Spryloom for the people I invite". It publishes single HTML pages and the files Claude writes. Folders on your computer need the command line:

npx -y spryloom publish

In Claude Code, add the plugin once:

/plugin marketplace add spryloom/claude-plugin
/plugin install spryloom@spryloom

Spryloom publishes apps and pages built with a coding agent behind sign-in, for the people you invite. This article was written by the people building it.

Get started free