Why this page exists
It answers "what can this product do at all" and shows which capabilities combine into working processes. If you need steps rather than an overview, start with Grant access and share a link or reading routes.
Capabilities
| Capability | Category | Task | Result | Combines with | More |
|---|---|---|---|---|---|
| Create a board | Start | begin work | a board from a template or empty | canvas, access, templates | Create a board |
| Canvas and objects | Canvas | assemble visual material | a board with sticky notes, shapes and text | frames, connectors, export | Canvas: what it does and where it stops |
| Access and roles | People | set permissions apart | a role on the board | link, export, agents | Access: roles and granting |
| Public link | People | show the board to people outside the team | a link with a password and an expiry | access, export | Grant access and share a link |
| Saving and offline | Data | not lose work | server confirmation, an offline queue | collaboration | Saving and offline |
| Export and backup | Data | take out and restore | PNG/PDF, a JSON backup, import | access, connectors | Export and backup |
| Connectors | Connectors | show dependencies | a line with an anchor and routing | canvas, agents | Connectors |
| Frames and kanban | Structure | structure work | sections and columns with cards | canvas, facilitation | Frames and kanban |
| Cards, tags and links | Structure | see work and sources | status, assignee, date range, tags, link | kanban, access | Cards, tags and links |
| Presentation | People | run a meeting | slides from frames, presenter and followers | facilitation, access | Presentation |
| Collaboration | People | work together | cursors, presence, follow, comments, reactions, lock | access, saving | Collaboration |
| History and trash | Data | undo and bring back | undo/redo, trash, copy | canvas, export | History, trash and copies |
| Agents | Extensions | delegate routine work | a task, a change set, a journal | access, events | Agents |
| Facilitation | People | run a meeting | a timer, voting | access, collaboration | Facilitation |
| Events and webhook | Extensions | react to changes | a signed webhook, retries, DLQ | agents, tokens | Events and webhook |
| Integration tokens | Extensions | act without a browser | a token with limited access | webhook, commands | Integration tokens |
| Apps | Extensions | extend the panel without code | a declarative panel | events, tokens | Apps |
How it adds up to a process
A typical cycle: gather material on the canvas → structure it with frames and kanban → grant access to the team → take the result out as a file. When the work has to repeat, agents, events and the webhook join the cycle.
Where to go next
If you are new to the product — reading routes. If you need exact rules — roles and capabilities.