In short, use projects when:
You need access control over data.
You don’t need in-depth comparisons between different areas.
and use branches when:
You’re testing multiple scenarios of the same park.
You want to do detailed comparisons of multiple areas (e.g., during screening or competitor analysis).
You don’t need to separate access to different parts of the data.
Projects
Each project is a separate workspace.
If you don’t need to carry out in-depth comparisons between different areas, creating separate projects is an excellent way to organise your work.
Configurations, components and GIS data stored in the organisation library can be shared across projects.
Another key benefit of projects is access control. You can manage permissions at the project level. This means that if someone should only have access to certain areas, you can structure those areas into separate projects.
👉 Read more about access control here.
You can also group projects into folders and apply access control at the folder level.
We recommend mirroring your team structure, for example, placing all projects within the same geographic area in one folder.
Branches
Branches are different canvases, or scenarios within a project, you can model as many scenarios as you want.
You can create multiple configurations and components within a project, and these are shared across all branches (read more about configurations here). As a configuration is applied to a specific park, you can easily create distinct scenarios and compare different setups within the same project.
The main advantage of using branches is that you can compare parks both within and across branches easily using the Compare tool.
Access control is managed at the project level, so everyone with access to the project can see all branches.
Branches can also be organised into folders, and when you’ve finished with a scenario, you can archive it without losing your data.