docs · the board
One list, wherever your team is looking.
Every pin is a task — title, description, severity, status, label, assignee and reporter; synced to one board per project.
Fields
| Field | Values |
|---|---|
| Severity | low · med · high · critical. Orthogonal to the label, because a feature request can be critical. |
| Status | open · fixed |
| Label | bug · feature · design, plus your team's own. The three built-ins are constants so they cannot drift into three different reds across three teams. |
| Assignee | Any member of the owning team. |
| Steps | The confirmed subset of the recording. |
Pin colour follows the label, so fifty markers on a page carry meaning at a glance instead of being fifty identical dots.
Teams, projects and keys
A team owns projects; a project owns sessions. Each project has its own write key, and that key in the script tag is what decides where a report lands.
team → projects → sessionsMembers join by email-matched invite and hold one of four roles — owner, admin, member, viewer. Custom labels belong to the team and can be created inline while filing. The key itself is never shown to a viewer, since holding it would grant write access their role does not include. Copy yours from Setup after signing up.
How syncing behaves
Publishing sends only what you actually changed, so you never overwrite a teammate’s newer edit to a task you merely happen to be holding. Deletes travel as tombstones, which is what lets the board shrink rather than only grow.