Projects, your way.
Run any project as a Kanban board, a Gantt timeline, or a matrix — all over the same underlying data. Subtasks, dependencies, custom fields, and templates that adapt to your workflow.
Anatomy of a project
A project is a container for tasks. Tasks belong to sections (the columns on a Kanban board), can have any number of subtasks, and carry any custom fields you've defined for the project type.
- Sections double as Kanban columns and Gantt swim-lanes
- Tasks have status, priority, due date, assignees, and a free-form rich-text body
- Custom fields support text, number, select, multi-select, date, and people types
- Comments are threaded; @mentions notify in real time
Views — Kanban, Gantt, Matrix
The same task data renders in three views without any extra setup. Switch via the view tabs at the top of any project.
Drag tasks between columns. Best for in-flight work.
Timeline with dependencies. Best for milestones.
Crosstab of any two custom fields. Best for capacity.
Templates per project type
Most teams have project archetypes that repeat — a tour, a venue, a corporate gig. Define a project template once, with sections, default tasks, custom fields, and people roles, and every new project of that type starts at 80% configured.
Statuses and automations
Statuses live at the project level — define the lifecycle that fits the work (e.g. Brief → Quoted → Booked → Done), not whatever a generic tool gave you. Automations can fire on status change to create tasks, generate an invoice, or notify a channel.
Permissions
Visibility is set at the team level. Members of a team see all of the team's projects; you can further restrict individual projects to a subset of members for client-confidential work.