KnitKnot

# Share your report

Create an evidence-backed issue report, review its draft, and publish or unpublish its public link.

## At a glance

  1. 1. **Choose a period**: Open its Reports tab and choose an eligible issue.
  2. 2. **Review the draft**: Check the issue, benchmark scope, captured answer, and supporting evidence.
  3. 3. **Publish**: Make the report live only after its preview is ready to share.

Reports begin as drafts in the console. Publishing gives a report a public URL that someone can open without a console account. Review its evidence and selected benchmark period before taking it live.

Open [Benchmarks → Results](https://app.knitknot.ai/benchmarks), select a benchmark period, then open its **Reports** tab.

## Create and publish an issue report

Select **Create report**. Search the listed **misrepresentation** and **reputation concern** issues, select one, and choose **Generate report**. Generation requires complete evidence for that issue and period; if it cannot complete, investigate the underlying [claim and evidence](/docs/investigate-a-claim/) first.

The new report opens as a draft. Read its preview, check the captured answer and evidence, then select **Publish report**. The report is live only after that action succeeds. A published report uses your workspace's hosted domain:

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

Anyone with that link can read a published report. A saved draft is not public. To stop sharing an issue report, open it and select **Unpublish**.

## Console report vs. public report

The console lets you inspect the issue report and its benchmark evidence. The hosted page presents the published report:

  • - **Console issue report:** the signed-in preview, with **Publish report** or **Unpublish** in the header.
  • - **Public issue report:** the read-only page at your `.knitknot.io` link, showing the finding, captured answer, and available source and company documentation evidence.

You may also see an older **head-to-head brief** in the Reports list. Its editor has a report period selector, **Generate report** or **Regenerate**, **Save draft**, and **Publish** controls. Review the generated preview before publishing. For an already live brief, **Publish changes** saves the updated selection to the public page. The current brief editor does not show an **Unpublish** control.

## What to share, and with whom

A published report is public to anyone with the link. Check its claims, period, and evidence before sharing it with a teammate or prospect. Keep an unfinished report as a draft.

For private workspace access, [invite a teammate](/docs/manage-team-access/) instead of publishing a report. You can also connect KnitKnot to your own AI tools with the [MCP integration](/docs/connect-to-ai-tools/), or revisit [issues and playbooks](/docs/issues-and-playbooks/) to act on what the report surfaced.

Docs navigation
Docs › Guides

Share your report

Create an evidence-backed issue report, review its draft, and publish or unpublish its public link.

Updated

At a glance

  1. Choose a period

    Open its Reports tab and choose an eligible issue.

  2. Review the draft

    Check the issue, benchmark scope, captured answer, and supporting evidence.

  3. Publish

    Make the report live only after its preview is ready to share.

Reports begin as drafts in the console. Publishing gives a report a public URL that someone can open without a console account. Review its evidence and selected benchmark period before taking it live.

Open Benchmarks → Results, select a benchmark period, then open its Reports tab.

Create and publish an issue report

Select Create report. Search the listed misrepresentation and reputation concern issues, select one, and choose Generate report. Generation requires complete evidence for that issue and period; if it cannot complete, investigate the underlying claim and evidence first.

The new report opens as a draft. Read its preview, check the captured answer and evidence, then select Publish report. The report is live only after that action succeeds. A published report uses your workspace’s hosted domain:

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

Anyone with that link can read a published report. A saved draft is not public. To stop sharing an issue report, open it and select Unpublish.

Console report vs. public report

The console lets you inspect the issue report and its benchmark evidence. The hosted page presents the published report:

  • Console issue report: the signed-in preview, with Publish report or Unpublish in the header.
  • Public issue report: the read-only page at your .knitknot.io link, showing the finding, captured answer, and available source and company documentation evidence.

You may also see an older head-to-head brief in the Reports list. Its editor has a report period selector, Generate report or Regenerate, Save draft, and Publish controls. Review the generated preview before publishing. For an already live brief, Publish changes saves the updated selection to the public page. The current brief editor does not show an Unpublish control.

What to share, and with whom

A published report is public to anyone with the link. Check its claims, period, and evidence before sharing it with a teammate or prospect. Keep an unfinished report as a draft.

For private workspace access, invite a teammate instead of publishing a report. You can also connect KnitKnot to your own AI tools with the MCP integration, or revisit issues and playbooks to act on what the report surfaced.