A dashboard an AI tool wrote is a web page. Sent as a file it may not open, may not render, and tells you nothing afterwards. Served as a link it stays a page, with the charts and the interactions intact, and the link decides who gets in.
Most companies have two audiences for the same document and one file to serve both. Make one link for the colleagues and one for the partner. They can serve the same document, and each carries its own rules and its own record of reading.
Inside the company: your domains, proved by a code
Switch on the e-mail gate for a link and list the domains that may pass, one per line. A reader types an address before the document opens; 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. Switch on the one-time code as well: without it, anyone who types a company address passes, and with it the reader has to open that inbox first.
Readers need no account. 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 end it, and the number of codes one address can ask for is capped, so the gate cannot be used to fill somebody's inbox. HTMLRadar stores only a hash of the code, never the code itself.
Verification is an option on the e-mail gate rather than a separate thing to configure. A domain rule on its own accepts any address typed in that domain, whoever types it; only the one-time code proves the reader owns the inbox. So switch the code on for any link where that matters, the internal one included.
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 e-mail when somebody tries, at most one every few hours for each link, so you find out if a partner is still passing the old link around.
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 Claude 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: in Claude, open Customize, then Connectors, press + and 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 tell 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. The address on a reading report is the mailbox that was let in; it is not proof of who read it.
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.