Claude built the planner or tracker, and now the whole team is meant to use it every day. Three things to settle before you send the link: where the data people type actually goes, who can open it, and how a new version reaches everyone. Plus the signs it needs a real backend instead.
You asked Claude for a capacity planner. Or a job tracker, a quote calculator, a pre-shipment checklist. It works. You showed your manager, and the answer was: good, the whole team uses this from Monday.
That changes the job. A page you show someone once only has to open. A tool a team opens every morning has to keep three promises: what people type into it ends up where they expect, only the right people can reach it, and the version everyone has open is the current one.
If you're still deciding where an AI-built page should live at all, where to host an AI-built page settles that in two questions. This page starts after it: the tool is self-contained (it runs in the browser, with no server or database of its own) and the audience is your team.
Ask Claude directly: "Where does this tool save what I type?" For most single-file tools the answer is localStorage, the browser's own small storage. That one word explains most of the surprises a team runs into in week one:
None of that is a bug. It's how a page without a server works. The question is whether it fits what your tool does:
| What the tool does with data | What to do |
|---|---|
| Each person works on their own: a calculator, a quote estimator, a personal to-do list | Nothing. Separate copies per browser is what you want. |
| One person owns the numbers and everyone else reads them: a weekly production plan, a status board | Put the data in the page itself. When it changes, ask Claude to rebuild the page with the new numbers and replace the file. Everyone sees the update on their next open. |
| People hand work to each other: a shift handover, a quote passed to a manager | Ask Claude to add Export and Import buttons that save to and load from a file. The file travels through your usual chat or email. Clunky, but honest about where the data is. |
| Everyone ticks off the same list | Shared ticks, below. |
| Several people add and edit the same records | That's a database. See the last section. |
One habit helps with every row: ask Claude to save the tool's data under a name specific to that tool (capacity-planner, not data), and to keep that name in every later version. More on why in the section on updates.
If what the team shares is "which of these are done", there's a lighter option on miinideck. Give each item an attribute like data-mn-sync="n1", upload the page, and a tick made by one person shows for everyone holding the link, within a few seconds. The page also shows who ticked last. The recipe is short enough to paste into the same Claude conversation that built the tool: tell it to put a stable data-mn-sync id on each tickable item, to style the done state with the class mn-on, and not to write its own click handler or storage for those items.
What it isn't, so you can decide quickly:
It's free on every plan, and it works on a password-protected page once the person has entered the password.
The link is a long random address that isn't listed anywhere and is kept out of search engines by default. Your teammates don't need an account, and nothing to install: they open it on a laptop or a phone like any web page.
For a team tool, add a password. It's free on every plan. Keep it wherever your team keeps shared passwords rather than in the same message as the link, so a forwarded link alone doesn't open it. What an unguessable link does and doesn't protect explains why the password still matters when the address is hard to guess.
When someone leaves, change the password and tell the team the new one. Anyone opening the link from then on needs it. A browser that already entered the old password can keep viewing for up to about four hours.
Be clear about what this is: one shared password for one link, not a login for each person. You can see how many times the link was opened, not who opened it. You can't give one colleague access and keep it from another on the same link. If the tool needs either of those, that's the last section of this page.
Replace the file behind the link everyone already has. Ask Claude for the change, take the new file, and in your miinideck dashboard open the page and choose Replace file. The address, the password and the expiry stay as they were. Anyone who opens or reloads the page gets the new version, and the previous one is kept for 30 days in case you need to switch back. Replacing a file you've already sent goes through the same move for a single page.
Two things to tell Claude every time it changes the tool:
data-mn-sync id as it is." If you use shared ticks, the progress is tied to the ids. Renumbered ids start from unticked.If you'd rather not leave Claude to publish, connect miinideck to Claude as a connector (MCP). Then you can ask Claude to publish the tool, or to update the one it already published, and it replaces the contents at the same address while keeping the password and expiry. One limit to know up front: the HTML travels through the connector as text, which caps it at roughly 100 KB in practice. A tool with images or charting libraries written into the file can go past that. For those, use the web uploader, or create a personal API token in Settings and run npx miinideck deploy. The link stays the same whichever way the new version arrives. Publishing over MCP has the details.
Upload the tool, add a team password, and send one link. Your free account includes one link that never expires.
A tool people bookmark has to stay at the same address for as long as they use it, so expiry is the part to check:
tools.yourcompany.com.Don't use the no-signup upload for a team tool. Those links last 7 days and the file behind them can't be replaced, which suits a quick share and not something people open every morning.
A private link serves a page. It doesn't run code on a server, and it doesn't hold a database beyond the on-off ticks above. That's enough for a lot of internal tools, and not for these:
| If the tool has to… | Why a link can't do it | What to use |
|---|---|---|
| Save records that everyone sees and edits: a shared order log, a booking board | There's nowhere for the records to live except each person's browser | A database-backed app on Vercel or Netlify, or an internal-tool builder such as Retool |
| Call another system with a secret key: an ERP, a pricing API, an AI API | Anyone who opens the page can read its source, key included | A small server that holds the key and calls the system for the page, on Vercel or Netlify functions |
| Give each person their own login, or show different people different data | One password opens the link for everyone | An app with sign-in on Vercel or Netlify, or Retool |
| Show live company data to people who all work in your Claude organisation | It doesn't need to leave Claude | Keep it in Claude with connectors. Sharing a Claude artifact that uses connectors explains when staying is the better shape |
Those tools are built for exactly that job and do it well. If your tool is one row of that table, take it there. If it's a planner, a calculator, a tracker one person keeps up to date, or a checklist the team ticks, it doesn't need a backend: it needs a link that stays put, a password, and a way to swap in Claude's next version without anyone noticing anything but the change.
It depends less on the AI tool than on the account you made it in. A table of who outside your organisation can open a shared ChatGPT, Claude, Gemini or Microsoft 365 Copilot link, whether they need an account, and whether your admin can switch it off. Checked against each vendor's documentation on 12 October 2026.
You sent a Claude Slides deck with 'anyone with the link' and your client got a sign-up screen. Why that happens, what Docs, Slides and Design actually export, and how to get the work in front of someone who will never make a Claude account.
You sent a client the public link to a Claude Code artifact and asked them to mark up what to change. There's nowhere to comment. That's by design. Here's the rule, which plans it leaves without a comment option for outside viewers, and how to collect pinned notes anyway. Checked against Anthropic's docs on 15 September 2026.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.