Project settings shape how projects and their tasks are classified. They're under Projects → Settings (project statuses/types/tags need the projects-settings permission; task taxonomy needs the task-settings permission). Projects → Settings opens on the first tab you can use, and shows only the tabs you can use.
Project statuses#
The project statuses — the stages a project moves through (for example Planning, Active, On hold, Complete). Some statuses are system statuses that drive completion roll-ups and can't be deleted, but you can still adjust their color and visibility. Add your own statuses to match how your team tracks project health.
Project types#
Types classify what kind of project it is — Website, Retainer, Onboarding, Campaign. Each has a name and color, and types are a useful filter and reporting axis.
Project tags#
Flexible, colored tags for any cross-cutting classification that isn't a status or type — SOW workstreams, campaigns, departments. Apply them on a project's edit form; they show as chips on the project cards, list, and record header, and the projects list can filter by tag (savable as a view). A common agency pattern: each SOW workstream becomes a tag, each deliverable becomes a project tagged with its workstream — so "how is Workstream 3 doing?" is one saved view.
Templates#
Project templates have their own page now: Projects → Templates. You build and edit a template like a project, with Day N dates, people or roles, a team and repeating tasks. See Project templates.
Workflows#
Projects → Settings → Workflows holds the rules that run on projects and tasks by themselves, such as warning the owner at 80% of the hours budget. They have their own permissions, so a delivery lead can run them without managing statuses and types. See Project and task workflows.
Custom fields and task fields#
Projects → Settings → Custom fields adds your own fields to projects (needs Project settings), and Task fields does the same for tasks in projects (needs Task settings). See Custom fields.
Task taxonomy#
Separately, projects have their own task taxonomy — task statuses, task priorities, and task tags — that the board and task panel use. This is scoped to projects (Planners keep their own), so you can tune how tasks are classified for delivery work without affecting other modules. One task status is the default new tasks start on. Built-in statuses can be the default too, but never one that completes tasks (new tasks would start finished) or an inactive one.
Task templates#
Task templates are reusable task setups: a name, a description, a checklist, and subtasks. You drop one onto a board instead of rebuilding the same task. There's one shared list for the whole organization. Projects → Settings → Task templates and Planners → Settings → Task templates show the same templates, so a change in either place shows up in both.
Anyone who works tasks can see the list and use the templates. Creating, editing, and deleting them needs the task-settings permission, the same one that governs task statuses, priorities, and tags.
System project statuses are the ones that make completion percentages and roll-ups meaningful — leave them in place and add alongside them rather than trying to remove them.