How do I share an AI-made dashboard with only certain people?

Inside the company: your domains, and nobody else

Switch on the email gate for a link and list the domains that may pass, one per line. A reader types an address before the document renders; an address outside your list is refused there and the document is never served. Two domains after a rebrand, or a subsidiary on its own domain, are just two lines. You can also list individual addresses, and a reader passes on either list, which is how one named person outside the company gets in without opening the door to their whole employer.

Nobody needs an account, on either side. Your colleagues do not sign up for anything, and neither do the people outside.

Outside the company: a one-time code

A typed address is a claim. Turn on verification for a link and it becomes a check: the address gets a six-digit code, and the document opens only when that code comes back. The code lasts ten minutes, five wrong guesses burn it, and the number of codes one address can ask for is capped, so the gate cannot be used to fill somebody's inbox. What HTMLRadar stores is a keyed hash of the code and never the code itself.

Verification is an option on the email gate rather than a separate thing to configure, so an internal link can stay a domain rule with no code to type, while the partner link asks for one. That is the difference the two audiences actually need.

Password, expiry, revoke, and replacing the file

A password can sit in front of a link as well as the gate, and it is meant to travel separately from the link itself. An expiry date switches a link off on the day you choose. Revoking one switches it off now: the document stops being served rather than merely being hidden, and anyone who tries the old address sees that it is no longer available. You get an email when somebody tries, at most one every few hours per link, so a partner still passing a dead link around is something you find out about.

When the numbers change, replace the file behind the link. Every link you have already sent keeps working and serves the new version the next time it is opened, and the reading you have already collected stays attached to it. The guide on updating a document after you have sent it covers what changes and what does not.

Publishing from Claude, without exporting anything

Add HTMLRadar to Claude as a connector and the model publishes for you. It can put a page it has just written behind a tracked link, make a second link of the same document for a different reader, replace the contents behind links you already sent, switch a link off, and read back who opened what. So the loop is: change the dashboard, ask Claude to publish the new version, and the address in everyone's calendar invite is still the address that works. The connector is at https://mcp.htmlradar.com/mcp, pasted into Settings, Connectors, Add custom connector. The connector page covers the other clients, which run a small npm package instead.

Which parts of the dashboard were read

A section counts time only once it has been at least half on screen for a continuous second, so scrolling past it records nothing. On a gated link that reading is attached to the address the reader gave, and on a verified link to an address that proved itself. Eleven seconds on the method and two minutes on the channel breakdown tells you which half of the page is doing the work.

What these controls do not do

A code proves that somebody had the mailbox open at that moment. It does not prove who read the page afterwards, and a forwarded screen is still a forwarded screen. Treat the name on a reading report as the account that was let in, not as an identified person.

A document is a web page, and a web page can run scripts and call out to other services. HTMLRadar serves every document in a sandbox on a separate domain, blocks it from submitting forms anywhere, and keeps it out of search results, which protects the application and the reader. It does not make it impossible for the document you uploaded to send something outwards. If a dashboard was generated against live data, look at what it calls before you share it widely.

Revoking a link stops the serving. It does not recover what a reader already has: screenshots, a saved page, a copied number in a spreadsheet. Nothing anyone sells can. What the rules change is who could reach the document in the first place, and what you know about them afterwards.

Common questions

Can I limit a shared link to everyone at my company domain?

Yes. Turn on the email gate for that link and list the domains that may pass, one per line. Anyone with an address at those domains gets in after typing it, and an address outside them is refused at the gate. More than one domain is fine, and you can add individual addresses alongside, which a reader passes on either list.

How do I share a Claude artifact with someone outside my company?

Export the artifact as HTML and publish it through HTMLRadar, or let Claude publish it for you through the connector. Then turn on verification for that link: the reader types their address, gets a six-digit code in their inbox, and the document opens when the code comes back. They need no HTMLRadar account and no Claude account.

Does the reader need an account to open the link?

No. Readers never sign up for anything. They open the link, and depending on how you set it they may type an address, a six-digit code sent to that address, or a password before the document renders. Accounts exist only for the people who publish.

Can I update a dashboard without sending a new link?

Yes. Replace the file behind the document and every link you have already sent serves the new version the next time it is opened. The addresses do not change, the gates and allow-lists stay as you set them, and the reading already collected stays attached. Claude can do the replacing through the connector.

Every control on this page is on the free plan too, for your first two links. AGPLv3 source on GitHub.