> ## 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.

# How Hebno works

> How Hebno reads your firm's documents and connects them to your CRM, ERP and finance systems, so you can ask about a client, not only a file.

Most search tools work on keywords and folders. If you don't know what a file is called or where someone saved it, you don't find it. Hebno works from meaning and from the client the file belongs to, so you can ask "what did we agree with Contoso on late delivery?" and get the clause, the deal it belongs to and the invoices that followed.

Hebno does this in four steps that run on their own every time a file is added or changed. A fifth rule applies to numbers, which Hebno never copies.

![Sources feeding four steps, Read, Label, Index and Link, into a client map, with CRM, ERP and finance looked up live](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/hww-pipeline.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=d0e08b6826fd10f1af417a9d0a40e5f3)

Documents flow through four steps into a map of each client. Business figures are looked up live.

## 1. Hebno reads everything you point it at

Connectors read from the places where your firm stores its knowledge: SharePoint and OneDrive, Google Drive, Dropbox, Box, Confluence, Notion, your project files and the workspace library. When a file is added or changed, it is read within minutes. Nobody uploads, moves or renames anything.

Hebno reads a document the way a person does, not as a stream of text. Headings remain headings, a table remains a table with its rows and columns intact, a scanned contract is read from the page image, and a slide is read with its title, its chart and its speaker notes. A pricing table in a proposal is therefore searchable as a pricing table, not as a jumble of numbers.

![A proposal page and a scanned page turned into a heading, an intact pricing table and readable text](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/hww-reading.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=5a98ae3ed631c38420471e12aa7eda26)

Layout is kept: headings, tables, scanned pages and slides are read as what they are.

Admins choose which sites, drives, libraries and spaces Hebno reads, and can exclude folders such as HR or partner-only areas. See [Organisation brain](https://hebno.com/docs/admin/organisation-brain.md).

## 2. Hebno labels each document

A model reads each document the way a new joiner would and records what it is:

| Label | Example |
| - | - |
| Client | Contoso Retail |
| Project | Contoso pricing review |
| Document type | Contract, proposal, statement of work, status report, board paper, meeting notes |
| Key dates | Signed 14 March 2026, phase 2 ends 6 November |
| Key amounts and terms | Fee, day rate, payment terms, liability cap |
| Status | Draft, final, signed, superseded |

This replaces the tagging and filing nobody does anyway. It also marks which version counts: when a folder contains `SOW_v3.docx`, `SOW_v3_final.docx` and `SOW_v3_final_signed.pdf`, the current one is marked and answers use it, while the older drafts remain findable when you ask for them.

![A signed statement of work with client, project, type, dates, terms and status labels, beside a stack of three versions](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/hww-labels.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=4447100bad6ae935979d869054f4ab9e)

Each document gets labels, and the current version is marked.

## 3. Hebno indexes by meaning, not only by words

Each document is split into short passages, and every passage is stored with the context it came from: the document, the section heading and the labels above. Each passage is stored as a mathematical fingerprint of what it means, which is the "vector" part. A search for "penalties for late delivery" finds a clause titled "liquidated damages", even though no word matches.

A normal keyword index runs alongside it, so exact terms still hit: a contract number, a product code, a person's name. Hebno searches both and ranks the results together, then reads the best passages in full before it answers.

![Search for penalties for late delivery returning a liquidated damages clause matched by meaning and a contract matched by keyword](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/hww-search.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=48667876a229075c8a17cd17c62be3ee)

A search finds the clause by meaning and the contract by its number.

## 4. Hebno links documents to your business records

Because each contract is labelled with its client, Hebno connects a Contoso contract to Contoso's deals in your CRM, its jobs in your ERP and its invoices in your finance system. Search stops being one big pile of files and becomes a map of each client: the documents, the people, the open work and the money, side by side.

To build this map, only names and identifiers from your business systems are stored, such as a client name, a deal number or a job code. Hebno does not copy the records themselves. Linking a project to its records on the **Brain** tab makes the connection explicit. See [Linked records](https://hebno.com/docs/projects/linked-records.md).

![Contoso Retail at the centre linked to documents, a HubSpot deal, an SAP project, Xero invoices, people and meetings](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/hww-client-map.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=7c62cd7a332da2e96e7ffc644a474dcb)

One client, everything connected: documents, deals, jobs, invoices, people and meetings.

## Numbers remain in their source systems

Hebno does not copy financial or delivery figures into its index. When someone asks about margin, budget burn, hours logged or what a client owes, Hebno looks it up live in the system that owns the figure, at the moment of the question. You always get today's figure, every number is cited to the record it came from, and any calculation shows its inputs. The model never produces a figure on its own.

![Chat answer showing 41 percent margin calculated from Xero revenue and SAP cost, each cited and marked live](https://mintcdn.com/hebno/n4ZjS29g8cTdiNHz/images/hww-live-numbers.png?fit=max\&auto=format\&n=n4ZjS29g8cTdiNHz\&q=85\&s=9b3acd9560140b58a68820ca9ece45f2)

A margin answer built from live figures, with each input cited and the calculation shown.

The same applies to anything personal or fast moving. Email, calendars, meeting transcripts and chat messages are searched live in each member's own account when a request needs them, and are never added to the shared index.

| Kind of information | How the information is accessed |
| - | - |
| Documents, decks, spreadsheets, wiki pages, project and library files | Read, labelled and indexed by meaning, updated within minutes |
| CRM, ERP and finance records and figures | Looked up live at the moment of the question, never copied |
| Email, calendar, meetings and chat messages | Searched live in the member's own account |
| The open web | Searched live, minus any sources your admins block |

## Access rules match the source

If someone cannot open a file in SharePoint today, they will not see it in Hebno either. Hebno records the permissions of every document it indexes and checks them twice: once when it searches, and again against the member's own access when it reads the document to answer. When access is removed in the source system, or a file is deleted, Hebno updates within minutes.

![Side by side search results for a delivery consultant and a partner, with one result hidden for the consultant](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/hww-permissions.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=28ae495ebb2a0ad1d6501fce3ae18b69)

Two people, one search. Each sees only what their own access allows.

The same applies to business systems. Live lookups run with the member's own account or with the team and data-area rules your admins set, so financial figures are visible only to the people allowed to see them. See [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md).

## Security

* **Your region**: your workspace and its index are stored in the EU or the US, as you choose. Admins can turn on only EU-hosted models when work must remain in the EU.
* **Names are masked**: names of clients, people, projects and amounts are swapped for placeholders before text reaches a model, and restored inside your workspace when the answer comes back.
* **No training**: your inputs and outputs are never used to train a model.
* **Encryption**: AES-256 at rest and TLS 1.2 or higher in transit.

Read more on the [Hebno security page](https://hebno.com/security).

## From a question to client work

The sources searched depend on your question: the index, a live system, the web, or several at once. A quick question gets a direct answer. Work that needs evidence from many places becomes a research run, with each step and source shown as it goes. Either way, every reply lists its **Sources**, and deliverables mark each finding as **Supported**, **Inferred** or **Uncertain**, so a person reviews the work before it reaches a client. Hebno writes back to another system only after you confirm a card.

```mermaid theme={"system"}
flowchart TD
  Q["Your question"] --> W{"Where does the answer live?"}
  W --> K["Knowledge index: documents"]
  W --> L["Live systems: CRM, ERP, finance"]
  W --> P["Your mail, calendar and meetings"]
  W --> B["The open web"]
  K --> A["Answer or deliverable with sources"]
  L --> A
  P --> A
  B --> A
  A --> R["You review"]
  R --> C["Confirm a card to write back"]
```

## Next steps

> [card] [Quickstart](https://hebno.com/docs/get-started/quickstart.md)
>
> Ask your first question and save a first deliverable.

> [card] [How integrations work](https://hebno.com/docs/integrations/index.md)
>
> What each connected system reads and writes.


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