What makes Brain different
What Gurusup does with your knowledge beyond finding text, shown with concrete cases, and where you see each part in the app.
For admins and anyone evaluating Gurusup who wonders why they should not just search their documents. Brain is Gurusup's company memory, and this page is about what goes into it.
Take one question: "What did we agree with this customer on price, and is it still current?" A search tool returns the HubSpot deal, three Slack threads and a contract PDF, and leaves the reading to you. Gurusup has already read all four, kept the facts, marked which one replaced which, and flagged the one it could not settle.
| What Gurusup does | Where you see it |
|---|---|
| Learns facts, not just documents | Sources (contribution per source, Total memories), Overview (Memories) |
| Knows which facts are current | In the evidence your assistant gets |
| Connects what it knows | In answers that draw on several sources |
| Surfaces real disagreements | Conflicts |
| Respects who is asking | Team, Sources, Queries |
| Asks people when it does not know | My requests (members), Ingest (admins), Team (contacts) |
| Gives your assistant skills | Skills |
It learns facts, not just documents
Gurusup reads each document and writes what it learned as pages of Brain, organized around people, organizations, projects and decisions. Each fact is stored on its own, tied to the source it came from. A Slack message that says "renewal moved to March" becomes a fact on the customer's page, next to the deal stage from HubSpot.
Where you see it. Each row on Sources shows how much of what Gurusup learned came from that source, and Total memories on Sources and the Memories card on Overview show the total. A memory is one fact. See How Brain works.
It knows which facts are current
When a source clearly corrects or replaces an earlier fact, with a later date or an explicit correction, Gurusup marks the older fact as replaced and keeps it in the history. A newer document alone does not replace a fact: Gurusup needs the evidence that one replaces the other. Your assistant is given the current facts.
Where you see it. In answers. There is nothing to manage. When Gurusup cannot tell which fact is right, it raises a conflict instead.
It connects what it knows
Gurusup links facts to the people, organizations and projects they are about. A question about one customer can then draw on the deal in HubSpot, the account plan in Notion and the channel in Slack, because all three point at the same customer.
Where you see it. In answers. There is nothing to manage: your assistant gets the connected facts together.
It surfaces real disagreements
Gurusup settles the clear cases itself: facts from different points in time, explicit corrections, and facts that apply to different scopes, such as two prices for two plans. When the Notion pricing page and a Slack message give different prices for the same plan and nothing says which is right, Gurusup raises a conflict.
Where you see it. Admins and members decide under Conflicts, members only the conflicts they can read. See Resolve conflicts.
It respects who is asking
Gurusup returns only what the person asking may read. A sales rep and a finance lead can ask the same question and get different evidence. Access comes from two layers: the categories an admin grants each person, and sources an admin restricts to named people. Admins read every category, but a restricted source only if they were picked for it.
Where you see it. Admins grant categories on Team and restrict sources from Sources. Under Queries, they see how each question was handled. See Roles and Restrict a source to specific people.
It asks people when it does not know
When the evidence is not in Brain, Gurusup says so instead of guessing. If a colleague is set up as a Gurusup contact, your assistant can ask Gurusup to send them the question over Slack or a call. Their reply comes back to Gurusup, which checks it before adding it to Brain, so it can answer the next person who asks.
Where you see it. Members follow their requests under My requests. Admins see them under Ingest and set up contacts under Team (Gurusup contacts).
It gives your assistant skills
A skill is a set of instructions your assistant loads when a task matches it, such as "prepare the weekly account review". An assistant can propose a skill someone wrote. It does nothing until an admin approves it.
Where you see it. Admins manage them under Skills. See Skills.
One memory for many assistants
Gurusup is not tied to one assistant. One person can use Claude and another ChatGPT, Cursor or Codex, and both draw on the same memory, each with their own access. An admin can also create an agent account for automated software. See MCP overview and Agent accounts.
What Gurusup needs from you
Brain only holds what Gurusup is given.
| What | Who | Where |
|---|---|---|
| Connect sources | Admin | Connectors overview |
| Upload files or import a wiki | Admin, member | Upload content |
| Confirm the first build | Admin | Quickstart |
| Set up colleagues Gurusup can ask | Admin | Gurusup contacts |
| Grant categories, restrict sources | Admin | Members and roles, Restrict a source |
What Gurusup does not do
- It does not write the answer. Your assistant does, from the evidence Gurusup returns.
- It does not link to the original. A citation names a page in Brain. See Sources and citations.
- It does not know what it was not given. Sources it cannot read, and items not shared with it, are missing from Brain.