Tasks
One board, your workflow
Tasks attach to the client and to the project, grouped by status on one board. Checklists, labels and priorities alongside, plus org-wide templates for the work that keeps coming back.
One board, grouped by status
Tasks sit grouped under the statuses you configured, in your order. It is not a kanban that fans out into columns — it is sections in the same list you use everywhere: terminal sections start folded, and sorting orders rows within a section, never across them. You choose which columns are visible (labels, assignee, priority, due date, checklist), saved per person.
Statuses, labels and priorities on your terms
The set of statuses is not a fixed list in code but tenant data under Instellingen: rename, reorder, recolour and extend it. Labels are org-wide with their own colour, and a high-priority task reads in loud red everywhere. So the board speaks your studio's language, not the one we happened to ship.
- Default status: where a new task lands.
- Terminal status: marks the task finished and stamps its completion time.
- Required contact moment: a status can demand a linked interaction, so 'done' can be made to mean 'discussed with the client'.
Checklists with progress in view
Every task carries checklists; progress shows as n/m on the card and in every list, turning green once everything is ticked. Items have a title and a markdown description, so the how sits with the what. A checklist you reuse becomes an org-wide template and drops onto the next task in one click.
Templates: define once, apply anywhere
Recurring work (onboarding, a monthly delivery) is captured as an org-wide task template: tasks, priorities, checklists and relative due dates. Apply it to a client by hand, or let it fire automatically the moment a client enters a given status. So every engagement starts complete, not from a blank board.
- Apply by hand, or automatically on a client status.
- Due dates count from the apply date, plus so many days.
- Assignment follows the client's current responsible, not a name fixed when it was written.
Overdue is loud, and everything lands in the trail
Work past its date is loud red everywhere: on rows, in counts and on the dashboard widgets, so it never fades into the list. Every meaningful change lands in the task's activity trail, with who and when. The actor's name is a snapshot, so a departed colleague's work never quietly becomes 'the system'.
Want to know more?
The documentation describes every module in detail, from installation to permissions.