Share an interactive HTML dashboard with stakeholders

Send a link, not an attachment. An emailed HTML file loses its charts in most inboxes and goes stale the moment you change it. Publish the dashboard as a page instead: the charts and filters keep working in any browser, a password or a company-email lock keeps it private, and when the numbers change you update the page and the link everyone already has shows the new version.

Why not attach the file?

Email clients and chat apps preview HTML attachments badly or not at all, many block the scripts that make charts interactive, and every revision means a new attachment and a "use the latest one" message. A screenshot or PDF keeps the look but loses the interaction.

Keeping it private

Two kinds of lock work for one-off dashboards:

• Password: checked by the server before the page is sent, so the content never reaches anyone without it. Share the password separately from the link.
• Company email: viewers verify an address at your domain before the page opens, and you can see which verified emails viewed it. Good for internal reviews where passwords get forwarded.

Avoid in-page JavaScript password prompts: the password sits in the page source. Client-side encryption tools (StatiCrypt, PageCrypt) are a sound do-it-yourself option for a single file.

Keeping it current

Publish once, then update the same page each week or month. On PubSpace you can stage the new numbers as a draft, check them, and press Sync to make them live. The previous version stays restorable for 7 days, and your Library shows how many times it's been viewed. If Claude or another agent builds the dashboard, it can publish and update it itself over MCP.

Side by side

Questions

More guides
How to share a Claude artifact as a link →
Let your AI agent publish web pages over MCP →