Skip to main content
Facts tell Hive what is true about your business. Rules tell Hive how you work: the standing instructions, the things you do the same way every time, and the situations where Hive should ask you first. Hive learns them from your decisions. They used to be called learned behaviours or execution memory. Rules are part of your own Business Brain: every member has their own, and only you can see or change yours. Workspace Owners and Admins cannot see another member’s. They apply to your own signals and actions. Open Business Brain → Rules (/brain?tab=rules). Older links to /memory open the same section.

Read a rule

Each rule is written in plain language, for example “When an invoice is 14 days overdue, you usually chase by email”. Select a rule in the list to see: Each rule also shows its kind:

On, off and suggested

Filter the list with All, On, Off and Suggested: Everything Hive learns by itself starts as Off or Suggested. It never turns its own rules on.

Change a rule

Rules never override safety. A rule cannot bypass role permissions, blast-radius policy, spend caps or the kill switch. When the kill switch is engaged, every rule that is on in the workspace — every member’s — is turned off. That is the one action that reaches past your own rules, and it only ever makes Hive more cautious.

Where rules come from

Hive learns from what you do, not from instructions typed into a box:
  • Approvals. When the same kind of action is approved three times within 30 days, Hive offers an automation. It never offers one for a B4 action, such as sending an email or issuing a refund, and a “send email” automation accepted earlier no longer shows or sends by itself (see Earned autonomy). Accepting it adds a Pattern rule — see Autonomy and blast radius.
  • Declined suggestions and failed checks. When you choose Do not run, or an action ran but could not be verified, Hive suggests an Ask first rule for that kind of action, in the Brain of the person whose signal it was. It takes effect once turned on. The rule is kept to the company or person the signal was about, in whatever script their name is written: declining a signal about one Arabic- or Japanese-named client never holds back signals about another.
  • Reflection. Hive’s hourly reflection can suggest rules it sees in your own work.
Rules were cleared by the Brain rebuild. When Hive rebuilt every member’s Brain, every learned rule was deleted, those that were on included, and there is no copy to restore. Hive learns them again: it replays the outcomes of your past actions, and new rules appear here as suggestions as your approvals and declines build up. Turn back on the ones you want. See The Brain rebuild.

Keep your rules healthy

  • Turn a rule off the moment it is wrong; it stays in your list and its history.
  • Review your rules after a change in pricing, process or responsibilities.
  • Prefer one clear rule over several with slightly different wording, and delete the duplicates.
  • Check Times used: a rule Hive never uses may be too narrow.
If you have no rules yet you will see No rules yet: as you approve, decline and correct Hive’s work, the rules it learns appear here.

Business Brain

The people, companies, deals and facts Hive knows.

Autonomy and blast radius

How approvals turn into earned automation.

Safety and control

Kill switch and policy.