KnitKnot

# Manage authority sources

Add company websites and documents that KnitKnot can use to check claims and support playbooks.

## At a glance

  1. 1. **Add a website**: Open Facts → Authority, choose Add website, and enter the site or documentation root.
  2. 2. **Check its coverage**: Review scope, platform, citation statistics, and the pages found by a crawl.
  3. 3. **Add documents**: Upload current company documents that can support claim checks and playbooks.

Open [Facts → Authority](https://app.knitknot.ai/facts/authority) to manage the company sources KnitKnot uses when checking claims and preparing playbooks. The page has **Domains** and **Documents** views. Its **Integrations** view currently says **Coming soon**; connect supported analytics and publishing services from [Settings → Integrations](/docs/connect-workspace-integrations/) instead.

## Add a company website

  1. 1. In **Domains**, select **Add website**.
  2. 2. Enter your website or a documentation root, such as `example.com/docs`. A source added here applies company-wide unless it was explicitly scoped to one product elsewhere.
  3. 3. Choose a **Platform** if you know where the pages are hosted. Otherwise leave **Detect platform** selected. The platform helps KnitKnot determine which future content changes it can safely recommend.
  4. 4. Select **Add website**. Use **Refresh websites** to start another crawl when you need the inventory updated; the control shows when a crawl is already in progress.

The source table shows **Coverage**, **Scope**, and **Platform**, plus **AI citations** and **Last cited** when those statistics load. Citation statistics can be unavailable even when the website source is connected. Search or filter by scope, platform, or coverage to find a source. Use its row menu to correct the platform later.

For example, add both your main product site and a separate help center if important documentation lives on another host. Then check [Your Pages](/docs/review-your-pages/) to see what the crawl found. Adding a domain does not prove that every page was fetched or that an AI engine will cite it; [Content → Access](/docs/check-agent-access/) shows fetch and crawler findings.

**Disconnect** stops future crawling for that website source. The confirmation explains that already crawled pages and historical evidence are preserved. Check the source before disconnecting a root that supplies current facts or pages.

## Add a document

Select **Documents**, then **Add document**. Upload a PDF, DOCX, Markdown, or plain-text file up to 5 MB. PDFs need selectable text and may have up to 100 pages. Keep the page open while the upload is being prepared.

The list shows each document's name, length, and added date. Open a document to inspect its pages or sections. A claim or playbook citation can open a particular page or section in that viewer. Use the row menu to **Download**, **Rename**, **Replace**, or **Remove** a document. Renaming keeps existing citations working. Removing stops the document appearing in new evidence searches; historical claims and playbooks retain their evidence record.

For example, upload a current product guide to support a capability claim, or a dated policy document to check an answer about compliance. Read the cited passage and its date before [approving a fact](/docs/review-and-approve-facts/) or deciding an AI answer is wrong. A file in Authority is supporting evidence, not automatic approval of every statement inside it.

Docs navigation
Docs › Guides

Manage authority sources

Add company websites and documents that KnitKnot can use to check claims and support playbooks.

Updated

At a glance

  1. Add a website

    Open Facts → Authority, choose Add website, and enter the site or documentation root.

  2. Check its coverage

    Review scope, platform, citation statistics, and the pages found by a crawl.

  3. Add documents

    Upload current company documents that can support claim checks and playbooks.

Open Facts → Authority to manage the company sources KnitKnot uses when checking claims and preparing playbooks. The page has Domains and Documents views. Its Integrations view currently says Coming soon; connect supported analytics and publishing services from Settings → Integrations instead.

Add a company website

  1. In Domains, select Add website.
  2. Enter your website or a documentation root, such as example.com/docs. A source added here applies company-wide unless it was explicitly scoped to one product elsewhere.
  3. Choose a Platform if you know where the pages are hosted. Otherwise leave Detect platform selected. The platform helps KnitKnot determine which future content changes it can safely recommend.
  4. Select Add website. Use Refresh websites to start another crawl when you need the inventory updated; the control shows when a crawl is already in progress.

The source table shows Coverage, Scope, and Platform, plus AI citations and Last cited when those statistics load. Citation statistics can be unavailable even when the website source is connected. Search or filter by scope, platform, or coverage to find a source. Use its row menu to correct the platform later.

For example, add both your main product site and a separate help center if important documentation lives on another host. Then check Your Pages to see what the crawl found. Adding a domain does not prove that every page was fetched or that an AI engine will cite it; Content → Access shows fetch and crawler findings.

Disconnect stops future crawling for that website source. The confirmation explains that already crawled pages and historical evidence are preserved. Check the source before disconnecting a root that supplies current facts or pages.

Add a document

Select Documents, then Add document. Upload a PDF, DOCX, Markdown, or plain-text file up to 5 MB. PDFs need selectable text and may have up to 100 pages. Keep the page open while the upload is being prepared.

The list shows each document’s name, length, and added date. Open a document to inspect its pages or sections. A claim or playbook citation can open a particular page or section in that viewer. Use the row menu to Download, Rename, Replace, or Remove a document. Renaming keeps existing citations working. Removing stops the document appearing in new evidence searches; historical claims and playbooks retain their evidence record.

For example, upload a current product guide to support a capability claim, or a dated policy document to check an answer about compliance. Read the cited passage and its date before approving a fact or deciding an AI answer is wrong. A file in Authority is supporting evidence, not automatic approval of every statement inside it.