Task board, all-tasks view, task properties, relationships, and workflow hooks.
Tasks are organization-scoped work items. The SaaS app exposes route-backed task pages instead of client-only tab state, with Kanban and all-tasks views.
Tasks are expected to carry:
Tasks can link to customers, assets, and future workspaces. Historical references should snapshot important customer or asset facts when a task becomes part of a formal document or workflow run.
Task status changes are intended workflow triggers. Workflow-specific state should live in workflow tables or link tables rather than growing the task table with automation columns.