Project types let different kinds of work follow different workflows. Use them when a service genuinely needs its own task statuses, project fields, task fields, approval behavior, or client notifications.
Understand the default project type
Every workspace has a default project type. It is the fallback for new projects and older work without a specialized type. Create additional types for distinct delivery processes rather than minor variations that would make project creation harder to understand.
The overview shows how many statuses and custom fields each project type contributes.
Configure the project type
Overview names the project type and identifies the default.
Project fields captures information that belongs to the engagement.
Task fields captures information repeated across tasks of this type.
Task statuses defines the workflow used in task tables and boards.
Client notifications controls client-facing updates associated with the workflow.
Design task statuses carefully
Drag statuses into workflow order and choose colors that help distinguish stages. Only one status should mark work complete. A status can also represent client approval and optionally carry an approval reminder cadence.
Status settings control both the task workflow and the special meaning of completion or client approval.
Changing a project type affects every project and task that uses it. Review status and field changes before saving, especially after people have begun using the workflow.
Continue exploring Work