Your report lives in the console behind sign-in, but the whole point of a gap report is that you can hand it to someone — a teammate, an exec, a prospect. Publishing a report gives it a public URL that opens for anyone with the link, no account required.

You publish from the Reports tab on the Runs page in the console.

Publish a report

Open the report you want to share and mark it published. That flips on a public page served from your workspace’s hosted domain:

https://{your-workspace}.knitknot.io/reports/{report-slug}

Anyone with that link can read it. Until a report is published, the link is inactive — publishing is the switch that makes it public, so nothing is shared by accident.

Console report vs. public report

Both views render from the same underlying benchmark data with the same components, so what a reader sees matches what you see:

• Console report — the authenticated dashboard. This is where you configure the report, drill into the evaluations behind every number, and manage issues and playbooks.
• Public report — the read-only page at your .knitknot.io link. It shows the assembled report — score, what AI tells buyers, head-to-head results, sources — without the console’s editing and management surfaces.

The public page assembles fresh from your data, so it reflects the report as configured. When you edit a published report, the public page updates to match.

What to share, and with whom

A published report is public to anyone who has the link — treat the URL as the access control. It’s the right artifact for a prospect (“here’s exactly how AI represents you today”) or an internal stakeholder who doesn’t need a console seat. For anything you’re still cleaning up, keep it unpublished until it’s ready.

Next: connect KnitKnot to your own AI tools with the MCP integration, or revisit issues and playbooks to act on what the report surfaced.