How Brain works
How Gurusup turns a document in one of your sources into Brain, your company memory, and an answer with citations, and who gets which answer.
This page follows one piece of content from the moment a source sends it to the moment your assistant cites it. Read it if you are setting Gurusup up, or explaining to someone else what it does with your data.
Sources feed Gurusup. Gurusup learns from them, writes what it learned into Brain, your company memory, sorts that memory into categories, and hands your assistant only the evidence the person asking may read.
1. Gurusup receives content from your sources
Admins connect sources. Members can open Sources to read about company sources and browse the catalog, and each person can connect their own tl;dv key once an admin turns it on. Each source brings in content in its own way:
| Source | What Gurusup reads | Guide |
|---|---|---|
| Slack | New messages, from the moment the app joins a channel. No earlier history. | Connect Slack |
| Notion | The pages you share, from the moment you connect. Import history brings in older pages. | Connect Notion |
| HubSpot | New and changed deals, with linked contacts and activity. Import history brings in earlier deals. | Connect HubSpot |
| Other connected apps | HappyScribe, Holded, ClickUp, Asana, Linear, Granola, tl;dv, Factorial, Sesame, Zernio, monday.com, Attio, Mintlify and Documentation.AI, each with its own kind of content. | Connectors overview |
| Webhook | Whatever your tool sends, when it sends it. | Send data with a webhook |
| Uploaded files | The files, once. There is no ongoing sync. | Upload content |
Gurusup saves every item as it arrived before it learns from it. Every fact can be traced back to that original. Admins follow each item on Ingest, where its details show three steps: Received, Learned and Ready to answer.
The first build
A new organization has no memory yet. Gurusup has nothing to answer from until the first build runs. In setup, an admin confirms it with Continue at the end of the sources step. After setup, nobody has to: Gurusup starts the build by itself once your content is prepared and at least one document is ready. The first build takes longer than later updates, and Gurusup cannot answer company questions until it finishes.
The first build reads a first batch of up to 25 ready documents: uploaded files and knowledge saved through your assistant first, then Notion, HubSpot, webhooks and Slack, then everything else. Gurusup adds the rest after your memory is active, so with large imports the first answers may not cover everything. After the build, new content is added on its own. The Quickstart walks through it.
2. Gurusup learns from what it reads
Gurusup does not just store documents. It reads each one and writes what it learned into pages of Brain, organized around what your company talks about: people, organizations, projects, decisions. Each page holds memories. A memory is one fact, backed by the document or conversation it came from. Some screens call it a claim.
Gurusup also links related facts, so it can gather what it knows about one customer or project from several sources at once.
Gurusup learns in rounds, so a new item can wait a little before it moves from Queued to Learning. Every status label is listed in Processing statuses.
Categories
While it writes a page, Gurusup files it under a category, a business area that decides who can read it. There are eleven: general, marketing, sales, finance, product, engineering, operations, customers, hr, legal and leadership. A page has one main category, and a section that belongs to another area can carry that area's category, so one page can be split between two audiences. Gurusup picks the category. You do not tag content by hand.
Changes, conflicts and held-back updates
Each time it learns something, Gurusup checks it against what Brain already holds.
| What Gurusup finds | What it does |
|---|---|
| A source clearly corrects or replaces an earlier fact, with a later date or an explicit correction | Marks the older fact as replaced, keeps it in the history, treats the newer one as current |
| Two facts that apply to different contexts | Keeps both |
| Two sources that really disagree, and nothing says which is right | Raises a conflict under Conflicts, for an admin or a member who can read the sources. See How conflicts work. |
| An update that fails Gurusup's quality checks | Keeps it out of your memory. The item shows Held back on Ingest, the original is saved and the team is alerted. |
3. Gurusup keeps your memory current
Edits. When a document changes in a source that stays in sync, Gurusup reads the new version and updates what it learned.
Deletions. When content is deleted at the source, for example a Notion page or Slack messages, Gurusup removes the knowledge that relied only on that item. Facts other sources also back stay. The item shows Waiting to withdraw, then Withdrawn, and Gurusup keeps the history of what the source said.
Disconnecting. Disconnect and Remove source stop Gurusup from collecting. They do not delete what it already learned. See Remove, disconnect and what stays.
People adding knowledge. Anyone in your organization can tell their assistant a fact and ask it to save it to Brain, your company memory. The assistant sends it with the add_company_knowledge tool, after you ask or confirm. Gurusup learns it like any other content, so it takes a few minutes and gets a category the same way. Knowledge saved this way cannot be viewed, edited or removed from the app afterwards. See Tools reference.
4. Gurusup gives your assistant the evidence
When you ask a question, your assistant asks Gurusup, which searches Brain. Gurusup does not write the answer. It sends back the relevant passages and facts, the titles and references of the pages they come from, and anything it looked for and could not find. Your assistant writes the answer from that evidence and is told to cite it. The wording, and whether citations show, depend on the assistant. See Sources and citations.
Who gets which answer
Everyone in the organization asks the same memory, but Gurusup returns only what the person asking may read. It checks on every question, so a change to someone's access applies to their next question without Gurusup learning anything again.
Categories cover the common memory: admins read every category, and members and agent accounts read only the ones an admin granted them. A new member starts with none. Restricted and Private sources cover knowledge for selected people: Gurusup learns from each in its own space. Private includes only the person who sets it; administrators are not included unless picked. Each source has one of these three settings:
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
When nothing the person may read answers the question, Gurusup says it found nothing. It does not say what it withheld. The full decision order is in Roles, and how to set it up is in Members and roles and Restrict a source to specific people.
When Brain does not know
If the evidence is not in Brain, Gurusup says so instead of guessing. It can also ask a person: if a colleague is set up as a Gurusup contact, Gurusup can send them the question over Slack or a call. Their reply comes back to Gurusup, which checks it and learns from it like any other content. What the colleague answers stays private. Members follow these requests under My requests, admins under Ingest.
What spends usage
Learning from new content spends your organization's usage: uploads, what sources send in, new versions, deletions, colleagues' answers and knowledge saved through an assistant. Asking questions does not. When usage runs out, Gurusup keeps answering from what it knows and new content waits as Paused until usage renews or increases. The details are in Usage and limits.