How to Use FlowBoards

A complete guide to visualising and managing work — from Spaces and Boards through to Bins, Flows, and Tickets.

Section 01

Spaces

Spaces are the top-level organisational environment in FlowBoards. Any organisation can have any number of Spaces to manage Boards, Bins, and Tickets.

To get started, click the hamburger menu top-left and choose Edit Boards › Create New Board. Give your Space a name — it will appear under your Organisation name. Spaces can be interlinked via hyperlinks or operated independently.

Once created, click the settings icon on the bottom-left toolbar to configure background colour, size, permissions, and business rules. Everything — Boards, Bins, Flows, WIP Limits — lives within a Space.

FlowBoards Space settings panel
How it fits together: Spaces contain Boards, which contain Bins. Tickets are added within Bins. Flows link the Bins and measure the movement of Work Items across the process. Tickets support unlimited hierarchies.

Unlimited Spaces

Create as many Spaces as needed — each can show different views of the same data or serve separate purposes.

Own Permissions

Each Space has its own permissions and settings, enabling teams to collaborate independently.

Shared Cursors

Real-time collaboration with shared cursors — like Miro or Mural, purpose-built for flow of work.

Interlinkable

Spaces can be linked together via hyperlinks, sharing elements across workflows or kept entirely separate.


Section 02

Boards

Boards are visual collections of Bins arranged with a background and title. They can represent a Kanban board, PDCA, Flight Levels, Scrum, or any other methodology — the only limit is your workflow.

ML2 workflow example
Example of an ML2 Workflow
Upstream workflow example
Example of an upstream workflow

Creating a Board

Enter Edit mode via the hamburger menu and select Edit Boards. Use the design tools on the left panel to begin.

  1. Draw your layout — Use the rectangle tool to create a background shape and add a title with the text tool.

Drawing a rectangle on the board
Personal board example
Example personal board with background image and Teleporter bin
  1. Add Bins — Use the shortcut A + B or the Bin tool on the left to add bins matching your workflow.

Adding a bin using toolbar
Bin naming in FlowBoards

Name Bins using the namespace convention: GroupName.BinName. For example: MyTasks.todo, MyTasks.doing, MyTasks.done.

Bins added to board before alignment
Bins with the same name always show the same tickets — even if deleted and recreated. Use Ctrl + Shift + V (Paste Special) to copy a board with a new group name for a clean slate.
  1. Align your Bins — Shift-click each Bin and use the Align tool on the right panel to align top edges.

Selecting bins
Alignment tool
Bins selected
Bins aligned to top edge
  1. Set equal spacing — With Bins selected, use the Dimensions tool and set Horizontal Gap to 10px.

Setting horizontal gap
Board after spacing applied
  1. Add a background image — Select the background rectangle and upload an image in the right panel.

Uploading a background image
Board with background image applied
  1. Make Bins transparent — Shift-select all Bins, scroll to Override Colour in the right panel, and choose transparent.

Override colour to transparent
Board with transparent bins
Adding title
Finished board layout

Teleporter Bins

A Teleporter Bin is shared across multiple Boards — any ticket placed in it is instantly visible wherever it exists. Create one by naming a Bin name.Teleporter, then copy and paste it to other Boards.

Kanban Maturity Levels

Kanban Maturity Level progression
ML2 CONWIP

Controlled Work In Progress

WIP controlled at system level. Work pulled forward but capped globally.

ML3 Pull System

Stage-level Pull

Each stage has its own WIP limits. Work pulled only when capacity is available.

ML3 + Dependency Lot

Advanced Pull with Parking

Blocked work parked separately, keeping active WIP clean and metrics accurate.

ML2-ML3 CONWIP board
ML2–ML3 CONWIP: system-level WIP control
ML3 Service Delivery Pull System
ML3 Service Delivery Pull System: stage-level WIP limits
ML3 with Dependency Parking Lot
ML3 Pull System with Dependency Parking Lot

Section 03

Bins

Bins are the core building blocks of workflows — each representing a stage or state a work item passes through. Two display modes: a linear list view and a spatial view (like sticky notes on a whiteboard).

Creating Bins

  1. Use shortcut A + B or the Bin icon on the left toolbar.

  2. Name using GroupName.BinName — the text after the dot is shown as the Bin label.

  3. Optionally, select an existing Bin from another Board you have permission to access.

Bin creation dialog
Selecting bin from another board
Bins added to board
Bins before alignment
Alignment panel
Bins after alignment
Dimensions tool for spacing
Equal spacing applied

Grouping Bins

Select the objects and click Group in the right panel. The group moves and acts as one object. Click Enter Group to edit an item inside.

Group button in right panel
Groups list panel
Nested groups example
Example of nested Groups on a Feature Dev board

Bins and Tickets

In the Bin options (right panel), choose which Ticket Types a Bin can accept. Tickets are added using the + sign on the bottom-left of the Bin.

Bin ticket type settings
Unchecking ALL to restrict ticket entry

Bin Actions

Select a Bin and choose Add Action in the right panel to configure automated behaviours on entry or exit.

Add Action option in Bin settings
Discovery Timeout setting
Available Bin Actions
  • Delete — removes the Ticket on entry
  • Archive — archives the Ticket on entry
  • Discovery Timeout — Ticket highlights when overdue
  • Set Date on move to this Bin — useful for Resolved Blocker/Bug bins
  • Set Date on move from this Bin — tracks when work leaves a stage

Bugs and Blockers Configuration

Bugs and Blockers configuration overview
  1. Create the Ticket Type — In Organisation Settings, go to Tickets and create a type called Blocker.

  2. Create a Resolved Blockers Bin — Give it a Spatial property; set Columns and Rows to 3×3.

  3. Set Bin Actions — Completed Date = Now on entry; Completed Date = Blank on exit.

Spatial bin settings
Bin action date settings
Ticket Types in Organisation Settings
Creating a Blocker ticket type
Ticket Markers settings panel
  • Set Parent to show a ❌ square marker when Completed Date is absent
  • Set Direct to show a ✔ square marker when Completed Date is present

When a child Blocker ticket moves into the Resolved Blockers Bin, the parent's ❌ disappears and the child shows ✔. Bugs follow the same pattern using a 🐞 icon.

Bug ticket type configuration
Bug ticket markers settings
Resolved Bugs bin with ticket markers

WIP Limits

WIP Limits display as three numbers: minimum / actual / maximum. Set per Bin from the right panel, or apply grouped limits across multiple Bins using the WIP Limit tool on the left.

WIP Limit display and settings
WIP Limit display: minimum / actual / maximum

Bins create Flow

Tickets flowing across Bins form a Flow. In Settings, choose Flows to define which Bins form a sequence. Then use the Reports tool in a Space to embed metrics charts. Flows can span any number of Boards or Spaces.

Flow metrics chart in a Space
Flow metrics chart added to a Space
Key Bin Capabilities
  • Unlimited Bins, copyable across Spaces with namespace conventions
  • Linear (list) or Spatial (whiteboard) view modes
  • Any size, colour, design, or background image
  • WIP limits per Bin, per group, or across swim lanes
  • Entry rules, exit rules, time-based rules, work item type filters
  • Parent–child relationships in any Bin or Space
  • All actions recorded; Replay Mode to review history
  • Import Bins and Tickets from JSON

Section 04

Flows

Flows define how work moves through a process by grouping and ordering Bins into a sequence. They automatically produce metrics based on ticket movement, and charts can be embedded directly into a Space.

To configure, go to Settings (click your profile image) and select Flows. Choose which Bins form the sequence. Flows can span Bins across any number of Boards or Spaces.

Available Metrics

Blocked ticket measurement
Throughput
Cost of Delay (COD)
Value delivered
Cumulative Flow
Custom reporting
Metrics can be viewed via
  • Dashboards within any Space
  • FlowMetrics tools
  • Live data in reports and custom analytics
  • Customised by Bin selection and data options

Section 05

Tickets

Tickets represent individual work items — Project, Idea, Epic, Story, or Task — at any organisational level. They support unlimited parent–child hierarchies and can be visualised across multiple Boards simultaneously with zero latency.

Zero latency

Tickets move instantly across Boards with their own transition animations.

Multi-team assignment

Assign to multiple individuals or teams, with separate watchers and customisable notifications.

Replay Mode

Play back all Ticket activity at any speed. Filter by work item, individual, or team.

Rich content

Full requirements, checklists, file attachments (PDF, PPT, Word, images), comments with @handles, and dependency visualisation.

Scales to 10,000+

Designed to handle enterprise-scale volumes across any number of Boards and Spaces.

Full history

All movement tracked with built-in timers. History remains accessible even after archiving.

Customisation options

  • Class of Service — Standard, Fixed Date, Expedite, Internal, or custom classes
  • Visual styling — colour, shape, decorators, borders, and dynamic indicators (blockers, bugs)
  • Work Item Types — any type across unlimited hierarchy levels
  • Movement rules — restrict transitions between Bins as required