#Organise your work

Projects, process areas and process groups give every process a fixed place, so a team can find its processes and see what belongs together.

#How the levels nest

flowchart TD
  P["Project<br/>name, description, icon, owner"] --> A1["Process area"]
  P --> A2["Process area"]
  A1 --> G1["Process group"]
  A1 --> G2["Process group"]
  G1 --> X1["Process"]
  G1 --> X2["Process"]
  G2 --> X3["Process"]

Level	What it is for
Project	The top level — for example a customer, a department or an initiative. It has a name, a short description, an icon and an owner.
Process area	A top-level topic inside a project that bundles process groups, for example "Sales" or "Finance".
Process group	Groups related processes within an area, for example "Order handling".
Process	One business process: its master data, its diagram, its forms and its versions. See Process master data.

#Create the structure

Open Projects in the Designer and create a project. Inside it you create a process area, then a process group, then the process. The order is fixed:

A process group can only be created inside a process area — an empty project asks you to create an area first.
A process can only be created inside a process group — an empty area asks you to create a group first.

You can rename areas and groups later. They stay in the order you created them — see Build the structure of a project.

#Go further

Create and manage projects — the project list, the project page and what its figures count.
Build the structure of a project — create, rename, duplicate and delete areas, groups and processes.
Find processes with search and favourites — the search fields and your favourites.

#Delete with care

Deleting a level deletes everything underneath it. Deleting a process area removes its process groups and every process in them from Chester — you can no longer open, restore or start any of them. There is no recycle bin.

#Not the same as catalog groups

Catalogs in the Execution app also have sections that the screen calls "process groups". Those are a different thing: they decide how processes are offered to the people who start them, and have nothing to do with where a process is kept in a project. See Collaboration.