Projects

A project is a container for tasks. It has a name, a description, a status, and optionally a parent.

Inbox

Every account has an Inbox project. It is not special machinery — it is a normal project marked as the default — but it is where a task goes when you do not say otherwise, including everything from the dashboard's quick-add box.

Treat Inbox as a landing strip, not a home. The routine is to capture into it and move things out later.

Status

Status	Means
Active	in flight
On hold	paused, still real
Done	finished
Archived	out of the way

The project list defaults to hiding archived projects; Include archived brings them back. Archiving is the reversible way to reduce noise — prefer it to deleting, which takes the tasks with it.

Nesting

A project can have a parent project, giving you a tree — a client with a project per engagement, a product with a project per release.

Nesting affects task lists: from a parent project you can roll up its whole visible sub-tree rather than looking at one level. The task list caps that at 500 tasks rather than the usual 200, and tells you when there are more, so a wide tree does not quietly truncate.

Templates

New project from template creates a project with its structure already in place, which is what you want when the same shape of work recurs — an onboarding, a monthly close.

Templates are made from existing work: turn a project you have already run into a template, and instantiate it next time. See Templates for the API surface.

What lives on a project

Tasks, comments, attachments, tags, custom fields, and links to other records. The View in graph action opens the project in the knowledge graph with its links drawn around it.

Deleting

Deleting a project is not the tidy-up tool. Archive removes it from view and is undoable; delete is not, and the tasks inside go with it. If the goal is "I do not want to see this any more", archive is the answer.