How to share an interactive dashboard or report with a client

The cleanest way to share an interactive dashboard or report with a client is to publish it as a single link they open in their browser — view-only, private, and rendered exactly the way you built it. Upload the HTML at shareable.page or run shareable publish, then send the link. No file to download, no app to install, nothing they can edit by accident.

When you ask an agent like Claude Code or Codex to build a report, you get interactive HTML — charts, filters, a real layout. The hard part was never building it; it was getting it in front of someone outside your team without it falling apart. This walks through doing that well.

1. Publish the artifact

From the terminal, publish the file and give it a clear title the client will recognize:

shareable publish ./report.html --assets ./assets --title "Acme Q2 Performance"

Prefer clicking? Sign in, choose New artifact, and drop in the file or a zip. Shareable bundles the supporting assets, rewrites local references to private render URLs, and gives you desktop and mobile previews so you catch overflow before the client does.

2. Lock it down for an external audience

Client work usually shouldn't be wide open. Shareable artifacts are private by default — the link is an unlisted secret URL and the page is noindex, so it won't show up in search. For anything sensitive, add a password (hashed with scrypt) and share it over a separate channel. The artifact renders in a sandboxed iframe, and recipients never see download or source controls.

3. Send one link — and keep it current

Paste the link into your email or message. Because each artifact is versioned and the share URL points to the latest version, you can update the numbers next quarter and the same link shows the new report. You never have to send "v2_final" again.

4. Let feedback come back on the page

Recipients can comment directly on the shared artifact without signing up, so feedback lands where the work lives instead of scattered across email threads. A small views dashboard also tells you when the client actually opened it — useful before you follow up.

Why a link beats an attachment

A dashboard emailed as an HTML file or a zip breaks easily: asset paths go missing, it opens as raw code, or it looks like a developer artifact rather than a finished deliverable. A Shareable link sidesteps all of that — see Shareable vs sending an HTML file for the full comparison.