Boards

Boards are the shared surface for tracking work: kanban columns of tasks that people and agents move together. A board starts with To Do, In Progress, and Done columns you can rename, reorder, or add to.

The reason boards earn their place is that agent work and human work stay visible together. Without a shared surface, the agent’s weekly refresh lives on a schedule page, a teammate’s review lives in their head, and “where does the launch stand?” has no single answer. On a board, the agent’s card sits next to yours, moves through the same columns, and shows its run status while it works — so the team plans around agents the same way it plans around each other.

A concrete example — a product-launch board, two weeks out:

Task	Assignee	Priority	Notes
Finalize pricing	Dana	High	3 subtasks, 1 done
Draft launch announcement	Content agent	High	Blocked by “Finalize pricing”
Refresh competitor table	Research agent	Medium	Repeating task, runs weekly
Book the launch webinar	Sam	Low	Due June 12

Views and organization

Every board offers three views — Board (kanban), List, and Calendar. Archived tasks drop out of sight without being lost; Show archived brings them back when you need them.

In the Board view you can group rows into swimlanes by assignee, priority, or label; filter by the same; sort by priority, due date, or when a task was created or updated; color cards by priority or label; and choose what shows on each card (priority, assignee, run status, due date, labels). Grouping by assignee turns the launch board above into a per-person — and per-agent — workload view; coloring by priority makes the two High cards impossible to miss.

Columns carry their own settings in the column menu. Give a column a Task limit and its header shows the count against the limit, flagging it when the column runs over. Mark a column as a Done column and tasks landing there count as finished.

Share in the board’s header sets who can see it: keep it to the people you add, or open it to everyone in the workspace. Someone you add individually can be given Can view, Can update tasks, or Can edit, which also lets them change the board’s columns and settings.

Tasks

Add tasks from any column, then open one to edit its details: instructions, priority, labels, when it’s due or how often it repeats, and — one level deep — subtasks with a done-count on the card. A task can also declare what it’s blocked by; blocked tasks wear a red badge until the blocker finishes. In the example above, the announcement draft wears that badge until pricing is final, so the whole team can see what it is waiting on.

Instructions matter most when the assignee is an agent. Write them the way you’d brief a new teammate:

Draft the launch announcement for the June release. Follow the voice rules in the Product handbook knowledge base, keep it under 600 words, and note anything that needs a decision from Dana.

Agents on boards

Assign a task to an agent from the Assignee row. By default the board starts the work for you: 90 seconds after you assign, the agent picks the task up, and a dated or repeating task waits for its time instead. Run now dispatches it immediately. While an agent works, the card shows a run status — Queued, Running, Succeeded, Failed, or Stopped — and a task an agent has claimed shows who is working on it, so a glance at the board tells you what’s in flight without opening anything.

Behind the scenes, assigning a task to an agent creates an assignment that the task owns: the board manages its schedule and instructions, and View assignment opens it. When a run of a one-off task succeeds, the board moves the card into its Done column. Deleting a task that owns its assignment deletes the assignment too, which is why its menu reads Delete task and assignment.

Board settings, in the menu beside the board’s name, controls this. Turn off Auto-dispatch on assign when assigning should only record who owns the work, or change Wait before starting to set how long the board waits before an agent picks up newly assigned work. The same dialog holds Automation rules: when a task enters a column, the board can assign an agent, round-robin across several agents, move the task to another column, set its priority, or set a field. A rule that assigns an agent when a task lands in “Ready” turns that column into a queue your agents pull from.

Repeating tasks

Give a task a recurring schedule under When and it becomes a repeating task. When a repeating task assigned to an agent reaches a Done column, it returns to the start of the board with its due date advanced, and leaves a completed occurrence behind in Done as the record of that cycle. The competitor-table task in the example works this way: each week the agent finishes the refresh, the task goes back to the start for next week, and the Done column keeps a trail of the weeks already covered.

A successful run does not move a repeating task by itself, since a run on schedule is not the same as the work being finished; the agent or a person moves it to Done.

Adopting an assignment

An assignment that already runs on its own — from a schedule, a webhook, or a manual run (see Schedules, webhooks, and triggers) — can be brought onto a board. Choose Adopt an assignment from the board’s actions menu, pick the assignment and a column, and the board manages its schedule from then on. Release from board on the task hands it back unchanged, and deleting an adopted task releases the assignment rather than deleting it: the assignment keeps running.

Issues

An issue is a task that carries an obligation: something is owed an answer. It has a type, a subject, a severity, a handle like WPI-7K3M2QX4, and a history of everything that happened to it. Every issue is a task, but most tasks are not issues. Automations open issues from evidence (a detector noticing a silent account, say), and people open them from intent.

Issues collect on the Issues page, the cross-board queue of typed work still owed an answer. It lists work nobody has taken first, worst first, and filters to open, unacknowledged, or a single type. From the queue or an issue’s own page you acknowledge it, snooze it, or close it with an outcome the issue’s type defines. An issue that hasn’t been placed on a board waits in Triage until someone accepts it into a board and column, or declines it. The queue is keyboard-workable: j and k move, Enter opens, a acknowledges, and ? lists the rest. Search finds an issue by its handle, so the one an agent reports when it files something is enough to open it.

Patterns that work

Launch board — a one-off push mixing human and agent tasks, with blocked by capturing the sequencing and swimlanes by assignee showing workload at a glance.
Operations board — repeating tasks assigned to agents, a Done column closing each cycle, and occurrences piling up as the record of what ran. The board becomes the team’s operating cadence.
Delegation queue — a column of tasks written as briefs, with an automation rule that round-robins each new arrival across a few agents; run statuses show what’s in flight.
Editorial calendar — content tasks with due dates and labels by type, reviewed in the Calendar view when publish dates drive the plan.