/brain). It has six sections. People, Companies, Deals and matters, Facts and Rules each show a count; Automations shows its count once you open it:
The section, the view and the selected entry are kept in the page address, so you can bookmark or share a link
to them. Older links to the What Hive knows and Learned behaviours tabs still open the Brain.
The Business Brain is an optional product, on by default for new workspaces. An Owner or Admin
can hide it under Settings → Products → Company knowledge (Show Company knowledge in this
workspace). Existing workspaces keep their setting. Hive keeps learning while it is hidden, and
Ask still uses what it knows. If you do not see it in the sidebar, ask an Owner or Admin. See
Workspace settings.
The Brain moved to one per member in October 2026. The earlier Brain, which was shared across each
workspace, was deleted in every workspace together with its learned behaviours, and there is no copy to
restore. Each member’s Brain fills in again from the accounts they connect. Your connected tools, chats,
files and signals were not affected.
Browse people, companies and deals
People, Companies and Deals and matters each open on a list. Type in Search your Brain to narrow it: the search matches names, types, fact names and values, and relationships, and every word you type must match. Select an entry in the list to see, beside it:
On a phone the entry shows below the list instead of beside it, and Hive scrolls down to it when you select one.
The Facts section lists every fact in your Brain in one place, with the entry each one is about, and the same
search, which also matches the app a fact came from. It shows the first 200 matches; search to find the rest.
See the map
Choose Map beside the search to see the same Brain as a graph, and List to go back. The map draws at most 40 points at a time: the ones closest to what you selected, or to your business when nothing is selected. When it leaves some out it says so, for example “Showing the 40 closest of 177”. Select something on the map, or pick an entry in the list first, to centre the map on it. Opened without a selection, the map shows the whole picture and opens your own business’s entry when it has one; it never opens some other entry for you. On the map:- Filter by department to see one part of the business.
- Double-click a point, or press F while it has keyboard focus, to see just its neighbourhood. Choose Exit focus to return.
- Select a point to see its facts, baselines and relationships beside the map.
- With nothing connected, Connect an account opens Integrations.
- With something connected, a line names what Hive is reading, such as “Hive is reading your Outlook and Xero. Facts will appear here shortly.”, with View connected accounts to see them in Integrations.
See your automations
Automations lists the agents and workflows that are live for you: every Agent Studio agent that is deployed and every workflow that is deployed or has a schedule switched on. A paused one stays in the list, marked Paused. Drafts and archived ones are not listed. You see the ones you own and the ones shared with you, exactly as Agent Studio and Workflows show them to you. A live or paused workflow is described by its deployed release, which is what runs: a change you have saved but not deployed shows here once you deploy it. For each one the list shows:
Agent run counts and times cover the runs you started. Workflow runs cover your own runs and the production runs of
workflows you can open, or every member’s if you are a workspace Owner or Admin, as in the workflow’s run history. The list never shows a run’s inputs or results. Select a
name to open it in Agent Studio or Workflows. Search matches names, owners, apps, actions and triggers. If you cannot
use Agent Studio, Workflows or Scheduled in your workspace, that part is left out here too.
Choose Map to see the same automations as a graph. Each app is a hub, joined to every agent and workflow that uses
it: a dashed line when it only reads from the app, a solid line when it acts there. Pick an app from Centre on
an app, or select its hub, to centre the map on it and list everything that touches it beside the map, such as every
automation that reads or sends Gmail. Like the Brain map, it draws at most 40 points, the closest to what you
selected.
Read an entity’s brief
Select a person, company or deal — on the map or in the list — to see its Brief: the same briefing Ask Hive reads before it answers about it.- Facts with trust notes. On the map, each fact shows where it came from — the app’s name, such as Microsoft Excel — and when, and says when it may be out of date (older than 90 days), has low confidence, or was corrected by you.
- This is wrong. Choose it beside a fact, type the right value and choose Save correction. Hive saves your value as your correction (the same as Edit below), so later collection from your tools does not overwrite it. A correction by an Owner, Admin or Department lead is stored as Verified, and one by an Operator as Reported. Operators and above can correct; Viewers can read.
- Timeline. Drag the timeline back, or press play, to see what your Brain held about it at the end of an earlier day. Drag it to the end to come back to today. Values from an account you have since disconnected are never shown.
- Changed in the last 30 days, old value to new.
- Track record — your own past actions on it, each with its date, how it went, and whether you approved or declined it and why.
- Ask about this opens Ask Hive with a question about it ready to send: what you know, what changed, and what to do next.
- Teach a rule — write a rule about it in your own words, such as “Always chase Acme by phone, never email”, and choose Save rule. It becomes one of your rules. For a Lead, Admin or Owner it is on straight away. For an Operator it is saved as a Suggested rule: Operators cannot turn rules on, and your rules are yours alone, so Hive does not act on it by itself. Viewers do not see it.
Edit or remove a fact
When a fact is wrong, correct it in your Brain:1
Find the fact
Open the person, company or deal, or search the Facts section.
2
Choose Edit
Type the right value and choose Save. The fact now reads “Changed by you on …”.
3
Or choose Remove
Confirm with Yes, remove it. Hive stops using the fact.
- Your correction sticks. Hive does not overwrite a value you corrected: neither the hourly collection from your connected tools nor Hive’s own learning replaces it. To change it, edit it again. If the error lives in a connected tool, fix it there too, so other people and systems see the right value.
- A removed fact can come back. If a connected tool still reports a fact you removed, Hive can learn it again on a later run. Only something the tool saw after you removed it brings it back: Hive going back over earlier mail, or a tool sending an old record again, does not. To keep a value Hive should not use, edit it to the right value instead of removing it.
- Who can edit. Operators, Department leads, Admins and Owners can edit and remove facts in their own Brain. Viewers can read their Brain and every fact’s history but not change it. Nobody can edit another member’s Brain, whatever their role.
Your company’s register facts
When an admin has linked your firm to its Companies House record, Your business shows the register’s facts first: registered name, company number, status, type, incorporation date, registered office, SIC codes, and when the accounts and confirmation statement are next due. Each reads “From Companies House · number, read on …” with the date Hive last read the register: when the company was linked, or when someone last pressed Refresh from Companies House. Hive does not check the register in the background, so that date, not a “may be out of date” note, says how current they are.- Read-only. They have no Edit, Remove, History or This is wrong: they come from the register, not from your Brain, so a wrong value is fixed at Companies House or by an admin relinking the firm.
- They replace website guesses. On those same details, what Hive guessed from your website during onboarding is hidden, and Ask does not offer to forget it; the rest of what your Brain holds about your business stays.
- Tell Ask by either name. When you tell Ask to remember or forget something about your company by its registered name, Hive uses Your business, not a new entry of that name.
- Every member sees them, Viewers included. If you have no Your business yet, Hive shows one with the register’s facts. They never count as something your Brain learned, so they are not in Changed in the last 30 days.
Tell Ask, and it updates your Brain
You can also teach your Brain in a regular chat. When you tell Ask Hive a fact about a customer, supplier, person, deal or your own company — “Acme’s payment terms are now Net 60” — or correct something it said — “That’s wrong, Jane left Acme in June” — Hive saves it to your Brain straight away. There is no review step. The answer then shows Saved to your Brain, with the entity, the fact’s name and the value (and the value it replaced, if any), and an Undo button. Undo puts the fact back as it was before. Ask the same way to remove one — “Forget Acme’s payment terms” — and the answer shows Forgot from your Brain with its own Undo.- Only your own words. The value saved is copied from the message you just sent, before any line break, colon or quotation mark: what follows one is treated as text you pasted or quoted. A message may start with a short lead-in such as Correction: or FYI:, or a label such as TEST: or QA:. When you reply to Hive’s list with just a choice, such as “1”, the choice you picked counts as your words too, so Hive can save its name or email address; nothing else in the list does. Nothing an email, file, web page, connected app or earlier answer says is ever saved or forgotten, even if it asks Hive to. Hive saves just the value — “Net 60” — under a short label, never your whole sentence.
- Answers to Hive’s own question are not facts. A reply that tells Hive which item from its results to use — “The Data Room is folder 14j2… from your listing above” — is used for the task at hand and not saved to your Brain, unless you ask Hive to save it. When Hive tried to save something you did not ask it to keep and could not, the answer does not mention it.
- Ask it to save a record. When your own words ask Hive to save something to your Brain — “Save this company to the Brain:” or “Add Northwind Ltd to my Brain.” — the details you type after it, on the same line or the lines below, count as your words too, so “Company number: 01234567” is saved. A test, sample or made-up company is saved like any other. An ask inside text you pasted or quoted, or a question such as “Did I save Acme to the Brain?”, does not count.
- Never a secret. A password, PIN, access key or token is never saved to your Brain, even when you ask.
- Nothing reversed. A value you negated is not saved, whether the negation comes before it or is part of it: “Acme isn’t on Net 30” saves nothing. Say what the terms are instead — “Acme is on Net 60” — or ask Hive to forget the old value. A value that only mentions a negation later on is still saved: “Net 30 without late fees”, “cash only, no cheques” and “not-for-profit” are facts.
- A known fact name, or a note. Hive keeps a fact under a name it knows when one fits what you said, such as
email,phone,domain,roleorcompany. Anything else is saved as a note on that entity, named after your own words in lower case: “Acme’s payment terms are now Net 60” savesnote:payment termswith the value “Net 60”. A note’s name can be up to 60 characters. “Forget Acme’s payment terms” finds and removes the note the same way, and saying the terms again replaces it. - Name who it is about. Say the customer, supplier or person in the same message — “Acme is on Net 60”, not “they’re on Net 60” — and Hive saves it to them, adding them to your Brain if they are new. If you did not name them, Hive asks who you mean. A name you type is matched exactly: “Site F2” is never saved onto “Site F1”, however alike the names look. To forget a fact, name both the entity and the fact: “Forget Acme’s payment terms”.
- It sticks, like an edit. A saved fact reads Told to Ask and is marked as changed by you, so later collection from your tools does not overwrite it. A forgotten one shows Forgotten in Ask in its History.
- Kept to this chat when you say so. Say “for this chat only”, “don’t remember this” or “just for now” and Ask saves nothing from that message to your Brain, and holds back on the next few messages in that chat too; to save something there anyway, start a message with “Remember”. Ask still uses what you said in that chat.
- Up to three changes per message, in your regular chats in the Hive app only. Agents, workflows, Slack, Teams and AI tools connected through Hive’s MCP server never change your Brain this way.
- Undo works while the change is the latest. If the fact has changed since, edit it on the Brain page instead.
- Your Brain only, and the same roles as editing. Operators and above; Viewers’ chats do not save facts. Nobody else’s Brain is ever changed.
One person across your tools
When a connected tool records someone’s email address — a CRM contact’s Email, say — Hive remembers that address as one of the ways to name them. A calendar invitation or another tool that names the same address then reaches the same person in your Brain, whatever capitals either side wrote it in, and whichever arrived first. An address that already names someone else in your Brain is never moved to a different entity — except a person only your mail added, who joins the tool’s record (see below) — and one member’s addresses never link another member’s records.People and companies from your mail
When Hive stores a message from your connected Gmail or Outlook mailbox, the people on it join your own Brain:- Who is added. The sender of mail you receive (when its From names one address), and the people in To and Cc of mail you send. People copied on mail someone else sent you are linked only if your Brain already knows their address, so a stranger can’t fill your Brain by copying in made-up addresses.
- Each person is found by their address. An address your Brain already knows — from a CRM contact’s Email, say — reaches that person. A new address becomes a Person named with the address, such as Stacey Fagan (stacey@example.com), holding it as their email. A display name never decides who someone is or takes over an existing name, so a stranger who borrows a contact’s name never lands on the real one. A display name that is not a plain name (a web address, or more than five words) is left out, and the person is named by their address alone.
- Their company. A person Hive adds from your mail whose address is on a business domain is linked to that
domain as an Account,
with the link works at — Stacey Fagan (stacey@acme.com) —works at→ acme.com. Free email domains such as
gmail.comandoutlook.com, and your own domains, get no company. - The latest thread with them. Each person has a last emailed fact with the date and the kind of thread, such as 6 Oct 2026 · Gmail thread or 9 Oct 2026 · Outlook thread. Hive keeps the thread’s id behind it, so Ask can open that thread. An older message never replaces a newer one. If you remove it, only mail that arrives after that adds it back. The subject and body of your mail are never copied into your Brain.
- The matters their mail belongs to. Hive also keeps which of your mail threads each person and their company were on, the newest 50 for each, by the thread’s id only: threads they wrote to you, and threads you wrote to them. Being copied on someone else’s mail to you doesn’t count. When you ask about them, Ask also shows the matters those threads are filed in, under Matters under way, as well as the matters they are named in. Only your own matters and your own threads count, matched by the exact thread. This appears only in your own Ask chats: an agent’s run (including one you start or test), a workflow step and Signals don’t get it.
- The meetings in that mail. When a thread carries a meeting invitation, Hive looks the meeting up on your own connected calendar by the invitation’s exact calendar id: your Google Calendar for a Gmail mailbox, or the same account’s calendar for Outlook. It keeps the link only when the invitation’s sender organises the meeting (or you sent it and organise it), the meeting is on your calendar exactly once, and it is a single meeting that hasn’t been cancelled. Recurring series aren’t linked. Ask then also shows, under Matters under way, the matters that meeting is filed in, with the same limits as above. Hive keeps only the meeting’s id and its link on your calendar, never its title, time or guests, and only for invitations it stores from October 2026 on.
- Skipped: you and your own addresses; newsletters, mailing lists and automatic mail (mail whose own headers mark it as a list, bulk or automatic message); no-reply, notification and receipt senders; any message addressed to more than 25 people; and personal or sensitive mail, see What stays out of your Brain. Viewers’ mailboxes add nothing, since Viewers can’t change their Brain.
- Only you see them. Like your mail, the people, addresses and links Hive learns from your mailbox are in your own Brain only — never in a colleague’s, whatever their role. AI tools connected through Hive’s MCP server don’t see them either; you see them in the Hive app and in Ask.
- Disconnecting. Disconnecting the mailbox removes the email and last emailed facts, the works at links and the threads and meetings it added; disconnecting the calendar removes the meetings found on it. The people and companies only that mailbox added are deleted too, with their history. One that something else also stands behind stays in your Brain, without what the mailbox added: a CRM or another connected tool that recorded them, a calendar event they attend, another of your mailboxes, or your own edit.
- When a CRM contact arrives later. If a CRM or another connected tool that isn’t a mailbox later records the address of someone your mail added on a record of a person — a contact, a lead, or a record the tool hasn’t typed — they become one person: the tool’s record, such as Stacey Fagan, keeps its name, and the address, the last emailed fact and the mail’s earlier facts move onto it. Where both say something under the same name, the tool’s value is shown and the mail’s is kept as history. What came from your mail stays yours only: colleagues never see it, and AI tools connected through Hive’s MCP server see the tool’s record without it. A works at link from your mail is kept only to a company your mail added, since MCP hides those; a link to a company the tool also knows is dropped. Disconnecting the mailbox later takes back what it added — you still see it in the person’s fact history, as with any disconnected app — and leaves the person, still found by the address the tool recorded. Facts you saved on the person yourself move with them and, now that the tool knows them, AI tools see those too, as they would had the tool recorded them first. A record of another kind that carries the address, such as a customer whose billing email is theirs, stays separate.
- New and earlier mail. Hive links the mail it stores as it reads it, including a newly connected mailbox’s first year of mail. Mail Hive stored before it started linking people is linked too, a little at a time: each sync of your mailbox works through up to 200 earlier messages, under the same rules, until it reaches the end. Only mail Hive stored on or after 8 October 2026 is linked this way. Older stored mail is not, because Hive didn’t record then whether you sent a message or whether it was a mailing, and Hive doesn’t fetch those messages again from Gmail or Outlook to find out. Since Hive started keeping threads (October 2026), each mailbox works through its earlier mail once more so their threads are kept too; that pass never brings back a fact you removed.
What kind of thing each entity is
Each entity has a type, such as Customer, Supplier, Contact or Account. An entity Hive first meets without one — a customer named on an invoice, say — shows as Unknown until a connected tool says what it is; the first type it learns sticks, and a later record never changes it. A company that a connected tool describes only as a “company” or “organisation” becomes an Account, so it is a node you can explore and trace connections through.Trace how two things connect
In an entity’s inspector, choose How is this connected to…, then search for a second entity. Hive shows the shortest chains of learned relationships between the two — each link written as a sentence with its role and, where recorded, the date it was learned. A record that appears only as the target of a relationship, and is not an entity of its own, is marked External reference. Hive looks for chains of up to four links and shows at most three equally short ones. Links through your own business entity, or through Hive’s own monitoring hub, do not count, because almost everything connects through them.Trust levels
Not every fact is equally reliable, and Hive does not treat them as if they were. Every fact carries a trust level, and Hive weights it accordingly when it answers questions or ranks signals:
A fact derived from several sources takes the trust of its least trusted source, so an inference can never be
more reliable than its weakest input. During onboarding, facts Hive gathers from your public website start as
low-trust context.
The same goes for each batch of activity Hive reflects on. What it learns from a batch is filed only under the
customers, people and other entities that batch was about, never under another one the model names. When a batch
mixes sources of different trust, or actions you decided with ones you did not, everything learned from it takes
the lowest trust in the batch, and counts as decided by you only if you decided every item in it (see
Learning from your own work).
Ask for a briefing, not a lookup
Ask Hive does not hand the model a list of rows: for every customer, supplier, person or deal your question names, it reads the Brain as a connected picture and briefs the answer with:
Entities linked to the ones you named get a shorter briefing (four facts, three links), and one answer covers at
most eight entities.
Three more questions the Brain answers directly in Ask:
- “How is Acme connected to Globex?” Hive traces the shortest chains of learned relationships between the two, the same search as Trace how two things connect.
- “What changed about Acme since 1 September?” Hive compares what it believed on that date with what it believes now and lists each value that moved, old to new, and each fact learned since. Without a date it looks back 30 days. Nothing a since-disconnected account contributed is ever shown, past or present.
- “What have we done about Acme before?” Hive lists your own past actions on Acme, newest first — each with its date, how it went, and whether you approved or declined it and why — so the answer can follow what worked and avoid what you turned down. It needs your connected apps, and shows only actions you took or approved, never a colleague’s. When Hive plans an action for a signal about Acme, it reads the same track record first.
brain_get_context tool of the
Hive MCP server.
How Ask finds what the Brain knows
When you ask a question, Hive picks up to five entities to start from: one whose name or alternative name is exactly what you asked, entities whose name contains it, entities named inside your question, and entities holding a current fact whose words your question uses — an invoice number, an email address, or a plain phrase such as “who pays promptly?”. Where a name embedding is available, a name close in meaning can also start the search. Those lists are combined so a match by name stays ahead of a match by meaning alone, and a name that is not close enough is never picked, so a briefing is not padded with unrelated entities and their open signals. The brief itself stays within a size limit, and Hive reads the entities the question reached rather than the whole Brain. When several names match, the closest comes first:- among names that contain what you typed, the one where it starts earliest, then the shortest name;
- among names mentioned in a longer question, the longest, most specific name.
How the Brain learns
Hive builds the Brain in the background:- Collect. Every hour, Hive reads fresh data from the tools and synced file stores you connected (Google Drive, OneDrive, SharePoint, Dropbox). Synced files keep the sharing permissions they have in the source. A file Hive cannot read (an unsupported type, or larger than 50 MB) is skipped, and if an edit makes a file it already holds unreadable, the old copy leaves the knowledge base rather than going stale.
- Reflect. Hive extracts facts, relationships and patterns from what it collected, and from the outcomes of your own actions. It compares each candidate with the facts and shadow rules it already holds for those entities, and adds it, updates it, closes a contradicted fact (the old value stays in the history), or leaves it when it only restates what is already known, including a rewording. Message metadata and placeholder names such as “Unknown” are not stored. What it learns goes into the Brain of the member whose account or action it came from, and no one else’s. All content is treated as untrusted data, never as instructions. Candidates with low confidence or only stale evidence are discarded. Proposed facts still have to use a known fact key, and a new rule stays in shadow until you promote it.
- Keep history. Writes never overwrite silently. When a value changes, whether Hive learned something new or you edited it, the old fact is closed — marked as replaced, corrected or removed — and the new one recorded, so you can always answer “what did Hive believe on that date?”. See Edit or remove a fact. When you disconnect an account, everything it contributed leaves the Brain’s answers, its earlier values included.
Facts need a known account
Every fact Hive learns from a connected app records the account it came from, so that disconnecting the account can take the fact back. Hive therefore adds facts and relationships from an app’s events only when it can identify the account they came from:- Apps Hive cannot identify an account for. Events from an app whose account Hive cannot identify add no new facts or relationships to your Brain. The event still starts your workflows and still counts towards Signals, and its files are still kept. Facts such an app added before this change stay in your Brain until you disconnect it.
- Messaging channels. Messages that reach Hive through Twilio, WhatsApp Business or Telegram are traced to the channel they arrived on, so they keep adding facts, and disconnecting the channel takes them back.
- Payment habits. How late a customer usually pays is learned from Xero only. See How late a customer usually pays.
Learning from your own work
Hive learns from the outcome of work on your own signals: signals from your own connected accounts, signals on your matters, and what Hive did by itself on an account you set to Act. That learning goes into your own Brain only, so only your Ask answers, briefs and the work Hive prepares for you use it. Nobody else’s Brain learns from it, and no Owner or Admin can read it.- Hive does not learn from a signal that involves more than one member’s accounts, from a signal whose member has left, or from someone else’s action on your signal.
- If one of the signal’s accounts is being reconnected or re-authorised, Hive waits up to six hours for it to come back and otherwise skips that outcome. Other members’ learning is never held up by it.
- Outcomes from before this was introduced are not replayed.
- Facts come only from what you decided. Hive keeps a fact learned from your work only when every outcome it came from was an action you approved or declined yourself. An outcome Hive reached on its own, such as an action it took by itself on an account set to Act, or an agent’s run, adds no fact to your Brain.
How late a customer usually pays
When you connect Xero, Hive learns how late each customer with an overdue invoice on one of your matters usually pays, and keeps it as an inferred fact on that customer in your Brain, for example “Usually pays 12 days late (median of 5 Xero sales invoices paid in full, the latest on 2026-09-14)”.- It is learned from at least three of that customer’s sales invoices paid in full in the last 12 months. Invoices settled by a credit note, and zero-value invoices, are not counted.
- Hive reads that paid history read-only, a few customers per read, longest overdue first.
- It is kept only on a person or company the matter already links, never on your own company.
- It is for you to read. Hive never uses it to set a signal’s severity, and never shows it to the run that drafts chasers or replies, so it never reaches a customer.
- Your own edit to the fact wins over it, and disconnecting Xero removes it. QuickBooks and FreeAgent are not read for this.
Learning from Ask answers
An Ask Hive answer is Hive’s own output, so it does not add facts to your Brain by itself: the hourly reflection run keeps a fact only when it comes from actions you approved or declined (see Learning from your own work). What Ask reads through your connected accounts, such as a live read from a connected tool, your mail or calendar, or a file synced through your account, stays in your answer. You still see the full answer. To put something in your Brain from a chat, tell Ask the fact yourself. See Tell Ask, and it updates your Brain.The Brain rebuild
Hive rebuilt every member’s Brain once, after it started keeping only facts under known names and recording the records behind each new fact. The earlier Brain had filled up with noise, so it was deleted rather than cleaned, and there is no copy to restore:- Deleted: every person, company and deal entry, with its facts, relationships, alternative names and mail thread links, and every rule Hive learned. Corrections you made to the old Brain were deleted with it, so correct a fact again if it comes back wrong.
- Kept: your connected tools, chats, files, signals and matters. A matter keeps the people it involves, by email address or by name, and finds them again in your Brain as they reappear.
- Refilled: Hive re-reads the mail it already holds from your connected mailboxes, newest first, and replays the outcomes of your past actions, so recent people and rules come back first. New facts are only kept under known names and with the records that back them.
”This Brain is still learning”
A new or freshly rebuilt Brain knows little. Until your Brain holds at least 25 current facts, under at least two different kinds of fact, what Hive reads from it — in Ask, for a company profile, and through the MCP server — carries the note This Brain is still learning. Answers that lean on the Brain may be thinner until then. The note goes away by itself as Hive learns.When an answer or signal looks wrong
1
Find the fact
Search for it in Search your Brain.
2
Check where it came from
Is it stale? Is it from a low-trust source? History shows every earlier value.
3
Correct it
Choose Edit, or Remove it, in your Brain. If the record is wrong in a connected tool, fix it there too.
4
Check the rule
If the fact is right but Hive acted on it wrongly, turn off or edit the matching rule in Rules.
Erasure and deleted workspaces
The Brain keeps history, with two exceptions where it deletes for good:- Erasing an entity. For a data-subject request, Hive can permanently erase a person, customer or supplier: the entity, every fact about it including superseded ones, its baselines and alternative names, and every relationship that names it. The person’s full name and email addresses are also replaced with “a removed person” in that member’s matters and matter Signals. An erase reaches one member’s Brain at a time, because every member has their own. It needs the Owner or Admin role, and your own business’s entity cannot be erased. There is no erase action in the app yet; an Owner or Admin can contact support. See Erasing someone from the Business Brain.
- Deleting the workspace. 30 days after a workspace is deleted, its Brain is permanently deleted unless the workspace is restored first. See Leaving Hive.
What stays out of your Brain
Your Brain is for your work: clients, suppliers, deals, matters and projects. Before your mail, events from your connected apps and meeting tools, or what Hive reflects from your work can add people, facts, relationships or learned behaviours to it, Hive checks the source and keeps personal and sensitive content out:- HR matters. Grievances, disciplinary and performance processes, one person’s pay or bonus, sick and fit notes, parental leave and whistleblowing.
- Health. Anyone’s diagnoses, appointments, treatment, medication or test results.
- Personal finance. Mortgages, personal bank and card statements, loans and debts, personal tax and pension statements.
- Family and personal life. Partners, children, school and childcare, family events and friends’ plans.
- Personal legal matters. Your own divorce or custody, fines, tenancy disputes, will, visa or police matters.
- Special-category data. Religion, ethnic origin, sexuality, trade-union membership, political opinions, genetic or biometric data and criminal records (GDPR Articles 9 and 10).
- Private consumer mail. Orders and deliveries, holiday bookings, utility and phone bills, and subscriptions.
The check leans towards keeping things out. The misses are mostly HR mail that never names the matter, such as a
note asking to handle “what we discussed with Karen” formally. What it keeps out by mistake is mostly business that
reads as personal, such as a firm’s work on a client’s divorce or mail full of health or HR words. A business item kept
out by mistake only means its people and facts are not added from that one source. The mail itself is still stored and
readable in Ask, and the same people are linked from the next business email that names them. Mistakes are more common
on items the check was never tuned on, which is the next thing we are improving. Baselines, the numbers Hive tracks
such as how late a customer usually pays, are not checked.
The check applies to what Hive learns from 3 November 2026. Facts learned before then are not re-checked: you can
remove any you don’t want, see Edit or remove a fact.
Who can see what
Your Brain is yours alone:- Only you see it. Your entities, facts, baselines, relationships and learned behaviours are visible only to you — on the Business Brain page, in Ask Hive, to an AI client you connect through the Hive MCP server, and to anything Hive prepares for you. Workspace Owners and Admins cannot see another member’s Brain, whatever their role.
- A chat you share shares its answers. Sharing a chat shares everything in it, including answers Hive built from your apps, files and Brain. Share only with people who should see that. See Feedback, sharing and history.
- Your accounts fill your Brain. What Hive reads through an account you connected — mail, calendar, or a company system such as Xero, HubSpot or Stripe — goes into your Brain only, even when the system is shared across the company. A teammate who connects the same system builds their own. An app whose account Hive cannot identify adds no facts; see Facts need a known account.
- Hive’s background work uses the owner’s Brain. When Hive prepares or plans for one of your signals, it reads your Brain, and a signal from your account follows your learned behaviours. Work that belongs to no member reads no Brain at all.
- Brain alerts reach only you. When a baseline in your Brain shifts (Baseline drift) or one of your learned behaviours goes live (Memory promoted to active), the alert appears in your own Today feed, not your teammates’.
- Your company profile is yours too. The business details you confirm during onboarding go into the Brain of the person who confirmed them.
- Your firm’s register record is shared. Once an admin links your firm to Companies House, its public register facts show on every member’s Your business, read-only. See Your company’s register facts.
Related
Rules Hive learned
Read, turn off, edit or delete the rules Hive follows.
Personal memory
What Hive remembers about you in chat.
Ask Hive
Ask questions grounded in the Brain.
Signals overview
How the Brain shapes signal priority.