Projects and teams
How to split projects and environments across your teams, and what they can share.
Give each product its own project, and give each team its part of a project with a resource group. Projects can share cloud accounts, modules and even running infrastructure.
Splitting projects and environments across teams
Split by product, not by team: create a project for each product or system that runs on its own (Project).
A project per product
For products that run independently, like a storefront and a recommendation engine.
An environment per stage, region or customer
Another environment of the same project, launched from its blueprint.
A resource group per team
Given to the team's user group, so each team changes only its own services and databases.
Link a cloud account or publish a module once, and every project can use it.
A dependent environment uses a base environment's resources, such as its network, cluster or database, instead of building its own. It runs on the same cloud account as its base, which can be in another project.
Access comes from user groups, and a group can have a different role per environment, such as read-only in production (Access control).