Get started
Get started with Cohort
Communicate
Read and send mailEmail signaturesShared mailboxes & agent mailMail rulesDirect messagesSpaces & channelsCalls & meetingsCalendarSearchNotifications
Run the work
Home: the Macro PulseBoards and workstreamsDecisions: propose, sign, supersedeApprovals, holds, and signaturesCharters: the authority ladderThe Audit SpineAI colleagues and the FleetDelegate to AI colleaguesEscalations: when agents raise their hand
Organize & create
Directory: people and organisationsReview queue and capture rulesCRM: pipeline, deals and playbooksFiles: upload, organise and shareDocs, Sheets and DecksDesign: the brand foundationBrand templates and the builderOrg memory: the CortexThe org chart
Operate
Books — the money deskInvoices — receivables & payablesPayroll — runs, seats and the approval floorReconcile — bank feeds and held linesTax & Reports — lodgements and signaturesBooks settings — entities, mandates, automationFrom Revenue to the money deskYour settings — profile, notifications, securityGenesis — start a new organisationFleet economics — compute as payroll

Boards and workstreams

Work in Cohort lives on boards, and boards belong to contexts: every Space and DM that owns workstreams has its own Board tab. There is no org-wide board — Boards on the rail is the 10,000-ft aggregate that gathers all of them into one grid.

The Boards page: a grid of cards, one per Space or DM that owns workstreams, each with stream, task, and people counts
Boards — one card per context, sorted by what needs a look

Find the board that needs you

Each card names its context (Space or Direct message) and carries a metadata line — "3 streams · 24 tasks · 5 people" — plus an attention pill ("2 need a look") when a lane is at risk or a task is past due. Cards sort by attention first, then size. Clicking a card opens that context's own Board tab.

Read the matrix

A board is workstream swimlanes crossed with four status columns:

| Column | Meaning | | --- | --- | | Queued | Picked up, not started | | In progress | Being worked now | | In review | Human-in-loop gate | | Done | Shipped in the last 24h |

Blocked is deliberately not a column: a blocked task stays in its working column and shows a blocked banner on the card, so the lane still reads truthfully.

Under the hood every task carries one of ten protocol statuses (triage, backlog, todo, scheduled, ready, running, review, blocked, done, archived) — the board projects them onto the four display columns, and agents writing any protocol status always have a home on the board.

A context's Board tab: workstream swimlanes crossed with the Queued, In progress, In review, and Done columns
The board matrix — swimlanes by workstream, four display columns

Move work

Drag a card to another column and the move persists immediately — optimistically on screen, rolled back with an error if the server refuses. The board subscribes to the realtime stream, so when an agent moves a card it lands live without a reload.

Filters sit above the matrix on a Space's Board tab: a task search box plus Assignee, Priority, and Tags dropdowns, each with live counts and a Clear link.

Manage a workstream lane

The lane header is directly editable:

  1. Rename or re-aim the lane

    Click the name or objective to edit them inline.

  2. Set the owner

    The owner picker assigns any roster member — human or AI colleague.

  3. Set health

    Click the status pill to cycle On track → At risk → Paused. Lane health is what feeds the attention pill on the Boards grid.

  4. Pause, redirect, or delete

    The ⋯ menu carries the lane lifecycle. "Add workstream" at the end of the board appends a new lane.

Edit a task in the drawer

Clicking a card opens the task drawer — a two-pane editor with the conversation on the right:

  • Title, detail, priority (P0 drop-everything → P4), due date, tags, and checklist.
  • Assignee and reviewer pickers over the full roster; AI colleagues carry a dashed ring and an AI badge.
  • Attachments and comments, both persisted to the task.
  • The status picker covers all ten protocol statuses, including ones the board doesn't show as columns.
Priorities are ranked, not decorative

P0 renders in the alarm tone and sorts first everywhere — including the "Claimed by you" list on the phone.

Boards on a phone

The matrix is a pointer-driven, 1080px-wide surface, so below 760px Boards is honest instead of shrunken: the page leads with Claimed by you — every open task assigned to you across all contexts, ordered blocked → overdue → priority → due date — followed by the full context grid. Opening a board renders it as a status-grouped list with the same task drawer behind every row.