Skip to main content

Automations

An Automation connects a trigger to actions. It is a generic rule that you configure; nothing is built per use case. Timers (scheduled and date-arrives) are fired by a workflow engine; other triggers run when the change happens. Each Automation has run history.

Authority, gates and limits

  • Authority is what a Member may do (read, write, manage) on a board.
  • Gates hold a proposed action until a person approves. If an Agent proposes an action and no Gate matches, the action runs at once, so every Template that lets an Agent propose also ships its Gate.
  • Limits cap an Agent, for example its budget.

Agents

An Agent in Work is a Member with its own authority, tools and knowledge, and a budget you can credit. You can run it on a cell, read its run history with trace and spend, and activate or deactivate it. Agents reach Work through the same API and through MCP tools.

Approvals

Pending proposals are listed in Approvals. Each shows who proposed it and what changes. Resolved proposals stay on the item’s timeline with who resolved them.