Skip to main content

​
What they’re for

It’s Monday. Someone drags “Launch landing page” from Backlog into In Progress, the owner gets a notification, and anyone glancing at the board already knows what’s moving and what’s stuck — no status meeting required. That’s the whole point: a board turns “where does this stand?” into something you can see in one look. And because an owner can be a person or one of your agents, work doesn’t stall the moment a human steps away. Boards are kanban boards — vertical columns with cards that represent tasks, which you drag between columns as you make progress. Unlike the CRM (which has pre-modeled funnel stages), a board is free-form: you create whatever columns make sense for your workflow. Typical use cases:
  • Backlog → In Progress → In Review → Done (project management)
  • Ideas → Approved → In Production → Published (editorial calendar)
  • Reported → Investigating → In Fix → Fixed (bug tracking)
  • Waiting → In Progress → Awaiting Review → Done (support flow)

​
Board anatomy

Columns

Each column is a state of work. You create, rename, reorder, and archive columns. No limit on the number — but more than 7–8 columns becomes hard to read.

Cards

Each card is a task. It has a title, rich description, owner, due date, priority, attachments, checklist, comments, and activity.

WIP limit (optional)

You can set a cap on cards per column. When exceeded, the board highlights it in red — a signal that there’s a bottleneck.

Card activity

Every action (column change, field edit, comment) is recorded on the card. Append-only history.

​
Card — full anatomy

Short title (what shows on the column). Rich description (markdown + WYSIWYG) supports lists, code, images, and mentions of leads/agents/members.
Owner is the primary responsible party — receives notifications and is accountable for delivery. Collaborators follow along but aren’t on the hook for delivery. Can be a person or an agent.
Due date is a date (not datetime — keeping the UX simple). Priority: Low / Medium / High / Urgent. Overdue cards get a red badge on the column.
Sub-tasks inside the card. Each item can be checked off independently. Useful for breaking “build feature X” into sub-steps without creating 10 separate cards.
Files (PDF, images, docs) or external links. Attachments count toward your org’s storage — see Settings → Storage.
Thread on the card. Mentioning @user sends a direct notification; @agent-name brings an agent into the conversation (e.g., asking Scout to research context).
Fields specific to the board (e.g., “Estimate in hours”, “Sprint”, “Associated client”). Apply to all cards in that board.

​
Views

Kanban

Default. Columns + cards. Drag-and-drop between columns.

List

Dense table with configurable columns. Good for analysis + bulk actions.

Timeline

Cards on a timeline (Gantt-style). Useful when due dates + sequence matter (launches, milestone-driven projects).

Calendar

Cards positioned by due date. Useful for editorial calendars / day-by-day planning.
At the top of the board:
  • Filter by owner — only my cards / only a specific person’s
  • Filter by due date — overdue / this week / no due date
  • Filter by tag / priority — combine multiple
  • Text search — substring in title + description
Filters can be saved per user — create “My overdue” once and it stays available in your menu.

​
Board vs. CRM pipeline

AspectBoardCRM Pipeline
ColumnsFree-form (you define them)Stages (with semantics — New / Qualified / Closed-Won / etc.)
CardsGeneric tasksLeads (person/company)
MetricsVelocity, WIP, lead timeConversion rate, cycle, pipeline value
When to useAny work with a flowSpecifically: sales / acquisition
You can have both in the same org — Board for internal projects, CRM Pipeline for sales.

​
How to create

1

+ Create → Board

Shortcut on Home, or right-click a folder → New board.Expected result: a modal asking for a name + initial template.
2

Choose a template (or start blank)

Default templates: Sprint, Editorial Calendar, Bug Tracker, Support, Launch. Each comes with columns + fields pre-configured.Expected result: board created with the template’s columns, no cards yet.
3

Add cards

Click the + at the bottom of a column, or use the shortcut ⌘Enter when hovering over the column.
4

Configure (optional)

Board settings → custom fields, WIP limits, automations, permissions.

​
Automations

The board can move work for you. Set a rule once and it runs on every card that meets it — examples:
  • “When a card moves to ‘In Review’, notify @reviewer”
  • “When the due date passes and the card isn’t in ‘Done’, mark it urgent”
  • “When a card is created, assign the default owner = whoever created it”
  • “When a card moves to ‘Done’, archive it after 30 days”
Configured in Board → Settings → Automations. No code — condition → action, IFTTT-style.

​
Audit

Every change to a card / column is recorded in the history:
  • card_created / card_moved / card_archived
  • column_created / column_renamed / column_reordered
  • field_updated (which field, value before/after)
  • comment_added / attachment_uploaded
Who did it + when + payload of the change. Append-only audit.

​
Next steps

Folders

Where boards live.

Tasks (mine)

Consolidated view of cards assigned to you, across boards.

CRM (pipelines)

The other type of “board” — lead pipelines.

Routines

For creating cards automatically on a schedule.