> ## Documentation Index
> Fetch the complete documentation index at: https://hebno.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems.
> Use British English (organisation, not organization).
> Every feature and integration described in these docs is available. Describe it as documented.
> Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only.
> Do not discuss commercial terms. Direct commercial questions to support@hebno.com.
> Start with /index and /get-started/quickstart.

# Sources and evidence

> Read the Sources button, citations and claim labels so you know what Hebno used, how well it is supported and what to check before client delivery.

Hebno attaches evidence to its work so a reviewer can see where each statement came from. Use the **Sources** button, the numbered citations and the claim labels to decide what is ready to send and what needs another look.

![Sources button open next to a claims list marked Supported, Inferred and Uncertain](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/sources-claims.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=b82497dc3cf4d2f2df5a022c65e3ab28)

The Sources list and the claims panel beside a reply.

## The Sources button

Under every reply and deliverable that used material, the **Sources** button lists each unique source once, with its logo or favicon. Open it to see:

* The name of the file, email, meeting, record or web page.
* A short excerpt of what Hebno used.
* A link that opens the original in its own system or on the web.

Each source has one of three kinds.

| Kind | What it is |
| - | - |
| **Internal** | Your firm's material: the library, firm files and firm systems |
| **Client** | Client material: project files, linked folders, client email and meetings |
| **Public** | The open web |

During a research run, the **Steps** trace shows the same items as **chips**, one per file or record, grouped by system, for example **Reviewing email** or **Checking context in SharePoint**. A chip shows **Cited as \[n]** when a document cites it, and **Findings backed** counts how many findings rest on a source.

> [!WARNING]
>
> Excerpts a reply used become part of the conversation. Anyone you share it with can read them, including excerpts from email, meetings and records.

## Citations

Documents contain numbered citations in the text, such as \[3]. Each number points to an entry in **Sources**. When you export a document, a **Sources** section is appended so the reader can follow every number. Decks do not include citations on slides. Their evidence is in the conversation's **Sources** list, and you can check a deck against its sources.

Documents come from the knowledge index, which updates from the source within minutes. Records, email and calendars are read live with your own permissions, so a source reflects the system at that moment. The excerpt it used is stored with the conversation, so the evidence for a deliverable remains available later.

## Claims

A research run breaks its findings into claims and labels each one.

| Label | Meaning | What to do |
| - | - | - |
| **Supported** | Backed by one or more cited sources | Spot-check the source for anything high stakes |
| **Inferred** | Hebno's reasoning from the material, not stated in a source | Confirm the logic, or rewrite it as your own judgement |
| **Uncertain** | An open question: nothing retrieved answers it | Find evidence, ask the client, or remove it |

Review **Inferred** and **Uncertain** claims first. Saying "likely" or "we estimate" in the client-facing text is a reviewer's decision, so make it deliberately.

## Verification state

Documents and decks show a shield that states how far they have been checked.

| State | Meaning |
| - | - |
| **From this conversation, not checked against sources** | Written from the chat, with no source check yet |
| **Checked against N sources** | A check compared the content with cited sources |
| **Edited since sources were checked** | Someone changed the content after the last check |

Select **Verify against sources** when a deliverable is unchecked or edited, or **Check again** when it is checked. Hebno runs a revision pass that compares the deliverable with its sources and updates the state. See [Verify against sources](https://hebno.com/docs/research/verify-against-sources.md).

## Blocked sources

Admins can block web sources by domain (including subdomains) or by pattern, for example `reddit.com/r/*` or `*.blogspot.com`, under **Admin → Organisation brain → Blocked sources**. Web search never returns or cites a blocked source. The rules apply to web search only. They do not affect the library, connected systems or files you upload.

## Reviewing before delivery

1. Open **Sources** and confirm the important figures come from the right system.
2. Read the **Inferred** and **Uncertain** claims and resolve each.
3. Follow two or three citations to the originals.
4. Run **Verify against sources** after your last edit.
5. Save the deliverable, or export it with its **Sources** section.

## Next steps

> [card] [Verify against sources](https://hebno.com/docs/research/verify-against-sources.md)
>
> Check a deliverable against what it cites.

> [card] [Research runs](https://hebno.com/docs/research/research-runs.md)
>
> How a run collects and weighs evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.