Checks built in
What Task & Kanban Board enforces at each step.
- Keep column, lane and task references within their board.
- Reject cyclic dependencies and unrecognized import mappings.
- Guest access needs board membership and a shared-task grant.
Create the board boundary and bring useful work into it.
Board Owner defines an active board, its timezone, ordered Columns, allowed source moves, optional Custom Swimlanes and Labels. Set each column’s wip limit and requires approval policy. Invite the intended internal roles through explicit board memberships. Proposed changes must preserve a valid column for every active task before a new workflow revision is accepted; archived columns with active work cannot simply be deleted.
Member creates a Task with a clear title, initial column, priority, optional planned start and due date. Owner is one active internal member; task assignees add collaborators without replacing accountability. Imports first validate column, lane, owner and date mappings in an import jobs preview. Board Owner accepts the mapping before execution; each source row creates at most one task under the same input identity.
Member adds task checklist items, marks mandatory steps and links any same-board task dependencies. Distinguish the blocking task from the blocked task. Reject self-dependency and cycles before accepting the edge. Shared work needs an explicit task participants grant and active guest board membership; a mention or pasted file URL cannot add that permission.
What Task & Kanban Board enforces at each step.
Start free, then use Proto to change fields, steps and approvals before your team goes live.