Create a project

Projects need Org plan.

A project belongs to an organisation rather than to an individual, so switch to the correct organisation before creating one. This is also why the projects list follows the organisation switcher, unlike workspaces.

Starting a project — title, description and who can see itOpen /p in the app

×

1. Open Projects and choose New Project.

2. Give it a title. This is the only required field.

3. Add a brief description. Optional. It appears beneath the title wherever the project is listed.

4. Choose visibility. Three levels, and the default is the closed one:

   	Who can see it
   Private (default)	Only people added to the project
   Organization	Anyone in the organisation that owns it
   Public	Anyone, including people with no account

5. Create the project. It opens at status Planning, with the creator as Owner.

Completing the project after creation

The creation dialog requests minimal information by design. Goals, members, milestones and budget are added after the project exists; there is no setup wizard to complete first.

The recommended order:

1. Milestones — the phases, which everything else hangs off.
2. Budget — categories with planned amounts, so spend has something to compare against.
3. Updates and evidence — as the work happens.
4. Reports — when someone asks.

Planning results applies alongside these and should be read before it is required, as the results-planning mode can only be advanced, not reversed.

Status is set manually

A project moves through planning → active → on hold → completed → abandoned. No transition is automatic: the status remains at Planning until it is changed, including after work has started.

Two consequences follow. A stale status presents the project as dormant to anyone reading the list, and a generated report describes the project as being at whatever stage the status records, since reports quote it directly.

Changing and deleting a project

A project’s details can be edited at any time. Title, description and visibility are all revisable, and a visibility change takes effect immediately for all viewers.

Deletion is soft. The project ceases to appear while the record is retained. Milestones, budget, updates and evidence are removed with it, so deleting a project in order to restart discards the history.

Where a project is finished or abandoned, set its status rather than deleting it. The completed and abandoned statuses exist for this purpose and preserve the record.

Project and update visibility differ

A project is created private. An update posted within it is created public.

The two defaults are opposed: restricting a project’s visibility does not restrict its updates. Check an update’s visibility before publishing rather than assuming it inherits the project’s.

Your projectsProjects