Automations
Automations are scheduled project-management routines. They propose a batch; a manager approves the run. Same proposal machinery as the assistant, different trigger.
Plan: Team and Enterprise.
Open Automations on a project to run a workflow now and review recent runs. Managers set hive-wide policy in Organization settings → Automations, then can turn individual workflows off for one project in project settings → Automations.
Workflows
Section titled “Workflows”Open How it works on each workflow in settings for the full rule. Short version:
| Workflow | What it proposes |
|---|---|
| Triage overdue | Each morning (hive-local 07:00), or when you run it on a project: for critically late unstarted work, move it into the first started column; raise priority to high (at risk) or urgent (critical). A manager approves the batch. Cap 40 actions. Same-day re-runs reuse that day’s proposals. |
| Weekly planning | If the project has no open “Weekly planning” task, propose one for this week — a checklist with open and overdue counts, due in two days. High priority if anything is overdue. |
| Auto-compile memory | Separate, off-by-default. Clusters useful Ask and assistant answers and writes them as draft notes / proposed decisions. Not an approval batch. |
| Assumption review | Each Monday (hive-local 07:00), or when you run it on a project: if a newer public project record (archived chat, transcript, note, or file — never private) settles an open assumption or unknown, propose updating that decision with a verbatim quote. A manager approves the batch. Cap 40. Same-week re-runs reuse that week’s proposals. |
Triage and weekly planning are rule-based (not a model) so a run cannot flood the hive. Assumption review uses the decision model only to judge evidence; debt scores on the project stay rule-based.
Trust policy (managers)
Section titled “Trust policy (managers)”Organization settings → Automations
- Master switch. Off means nothing runs, and project settings cannot turn a workflow back on.
- Require manager approval (keep this on until you trust a workflow)
- Which workflows are enabled for the hive. Off here hides that workflow from every project.
- An allowlist of tools that may auto-approve
- Auto-transcribe conferences and meeting AI actions (Team — see Meetings)
Project settings → Automations
Only hive-enabled workflows appear. Turn one off to skip it on that project. The hive list stays the source of truth.
A run is approved or rejected as a whole. Re-running the same workflow on the same day does not duplicate proposals (the hive remembers that day’s run). Tools on the auto-approve allowlist still leave a proposal row; Organization settings → AI → Oversight health counts them as ungated writes so the hive can see how often the gate is skipped.
Approved changes show up in task history and the project activity feed as the hive’s AI name when one is set (Organization settings → AI), otherwise as Ask, not as the manager who clicked approve. The manager still authorizes the write.
Turn automations on only after the hive already has real tasks and owners. An empty board produces empty theatre.
Related
Section titled “Related”Assistant · AI settings · Tasks · Plans