Skip to main content
As your organizationโ€™s IaC use grows, it is increasingly challenging to organize all resources. With the addition of env0 Sub Projects, you can now access additional layers of granularity to model even the most complex of deployment structures, and effectively manage your resources and configurations across different teams.

โœจ Sub Projects โœจ

Sub Projects allow you to create a hierarchy of projects to manage, helping create a hierarchy for your environments and configurations. Sub Projects have similar configurations to Projects but are nested within other Projects. Each Sub Project may have unique Environments, Templates, Variables, and so on. Once youโ€™ve set up your Sub Projects, you can view the entire project structure with ease. In the Projects menu, hover over Projects with an arrow next to them. This will allow you to see the Projectโ€™s Sub Projects. Clicking on the Project will let you see its environments or configurations.
Projects menu showing project hierarchy with expandable arrows for sub-projects
When choosing a Project, you may navigate to its Sub Projects page from the menu.
Project navigation menu with sub-projects page option highlighted

Creating a Sub Project

In the Sub Projects page, clicking on Create New Sub Project will open a modal for creating a standard Projects, but the created Project will be associated with the current Project as its parent.
Create New Sub Project modal dialog with project configuration form

RBAC for Sub Projects

Each Sub Project inherits the Roles from its parent Project down to the root Project. So for example, if a team was granted the โ€œView Projectโ€ permission, every person in the team would be able to view environment from the Project, its Sub Projects, its Sub Projectsโ€™ Sub Projects, and so forth This allows you to easily give users and teams permissions for multiple Projects, but also allows for granular permissions for specific Sub Projects For more information, please visit our docs
โŒ˜I