Introduction
What GuruSup Brain is, who does what in an organization, and what to expect before Brain can answer.
GuruSup Brain turns the documents, chats and records your team already has into answers. You get those answers inside the AI assistant you already use, with the pages of Brain's memory they come from.
How it works in practice
- An admin connects the places where your knowledge lives: Slack, Notion, HubSpot, your own files, or a webhook. Together these are Brain's sources.
- Brain reads that content and learns from it. The first time, an admin confirms this with Continue at the end of the sources step in setup, or with Build my memory on Home. Brain starts the build by itself when your content is prepared.
- Everyone connects their AI assistant to Brain once. Setup includes a short instruction that tells the assistant to check Brain first.
- From then on, when you ask your assistant about your company, it asks Brain and answers from what Brain finds.
For the detail behind each step, read How Brain works.
What you get
- Answers tied to your knowledge. Brain tells your assistant which pages of its memory an answer comes from, so it can name them. See Sources and citations.
- Honest gaps. If Brain does not know something, it says so. It can also ask a colleague who might know.
- Knowledge that stays consistent. When newer information replaces older information, Brain keeps track. When two sources disagree and Brain cannot settle it, an admin sees the conflict and decides. See Resolve conflicts.
- Access that follows your role. Admins can see every category. Members see the categories an admin grants them. A category is a label that groups knowledge, and access is granted category by category.
Roles and how people join
An organization has two roles: Admin and Member.
- The first admin. The person who signs up and creates the organization becomes its admin. Signing up takes you through the steps in the Quickstart.
- Everyone else joins by invitation. An admin opens Team, clicks Invite, enters an email address and picks a role. The invited person gets an email, signs in, and lands in the existing organization. They skip the Quickstart. See Invite your team.
- Changing roles. Admins can change anyone else's role, and choose which categories each member can see, on the same Team page. See Members and roles.
| What they do | |
|---|---|
| Everyone | Connects their assistant with Brain MCP, asks questions, and can set up their own Brain contact under Account |
| Admin | Also connects sources, starts the first memory build, invites the team, and manages skills, conflicts, queries, usage and settings |
| Member | Also follows the questions Brain asked colleagues for them under My requests, and answers Brain's questions if an admin or they themselves set up a Brain contact |
For the full list of what each role can open, see Roles.
What a Brain contact is
A Brain contact is a person Brain is allowed to ask when it does not have an answer. Setting one up is optional. Brain reaches a contact by Call or Slack, and the contact's topics tell Brain when to ask them. Without any contact, Brain still answers what it knows and says so when it does not know. Admins manage contacts under Team. See Brain contacts, and My requests for how a member follows a request.
Before you start
Admins need:
- A file to upload, or an app to connect (Slack, Notion or HubSpot). One is enough for the first build.
- An AI assistant that supports MCP. MCP is the standard way an assistant uses outside tools, and Brain connects to your assistant through it.
- The names or emails of the people you want to invite.
Members need:
- An invitation from an admin, sent to your email.
- An AI assistant that supports MCP. You connect it from Brain MCP in the sidebar, or follow Setup and authentication.
What happens before the first build
Until the first build has run, Brain has nothing to answer from.
- Your assistant can connect, but Brain tells it that Company Memory is not ready to answer company questions yet.
- Admin Home shows No sources connected yet with the source cards. On other pages, a banner tells admins: "Your company memory hasn't been built yet. Add content, then build your memory to start asking questions." Members see: "Brain has no sources yet, so it can't answer company questions. Ask an admin in your organization to set it up." After an admin confirms the build, Home shows "Preparing your documents." and the banner says "Brain is preparing your documents. Your memory will be built automatically when they are ready."
- Sources, Ingest, Conflicts, Skills, Synapses, Queries and My requests show "Available once your memory is built". Members are told "An admin in your organization needs to build it first."
Once the build starts, those sections open and fill up as Brain learns. The Quickstart walks an admin through the build.
Plans and usage
New organizations start on the Free plan. Free includes one seat, which is yours, and €5 of usage a month. Reading new content uses your usage. Asking questions through your assistant does not. Usage renews every month and does not roll over. To invite more people you need to upgrade: when the seat is used, Invite on the Team page offers an upgrade. See Plan and usage, Plans and quotas and Usage and limits.
What each source reads
| Source | What Brain reads | Guide |
|---|---|---|
| Slack | New messages in the channels you invite the app to | Connect Slack |
| Notion | The pages you share, and their changes | Connect Notion |
| HubSpot | Deals, with their linked contacts and activity | Connect HubSpot |
| Webhook | Whatever your own tool sends to the URL Brain gives you | Send data with a webhook |
| Uploaded files | The files you drop in, read once | Upload content |
See Connectors overview for how they stay up to date.
Works with your assistant
Brain works with the assistants listed under Need help setting it up? on the Brain MCP page: Claude, Claude Code, Codex, ChatGPT, Cursor and VS Code. It also works with any other assistant that supports remote MCP servers. Step-by-step pages:
For what the connection gives your assistant, read the MCP overview.
What Brain keeps
When Brain reads a document, it keeps the original content and writes what it learned as pages of its own memory. That is how every fact can be traced back to where it came from. Removing a source stops Brain from reading it. It does not erase what Brain already learned. See Check source status.
Next
- New admin: follow the Quickstart.
- Invited member: connect your assistant with Setup and authentication.
- Curious how it fits together: read How Brain works and What makes Brain different.