I know the security role terms are little confusing. Maybe it should read App Maker/admin but again it’s going to confuse Model-driven app makers who need System Admin/customizer roles to do their job. So Environment is right now used to deal with Canvas app and Power Automate (MS Flow) makers. Still Environment May or May not have CDS.
Read it as “Canvas powerapp maker role in current Environment”
Reference
- Environment Maker and Environment Admin are the only predefined roles for environments that have no Common Data Service database.
- The Environment Maker role can create resources within an environment, including apps, connections, custom connectors, gateways, and flows using Power Automate. Environment makers can also distribute the apps they build in an environment to other users in your organization. They can share the app with individual users, security groups, or all users in the organization. More information: Share an app in Power Apps
- For users who make apps that connect to the database and need to create or update entities and security roles, you need to assign the System Customizer role in addition to the Environment Maker role. This is necessary because the Environment Maker role doesn't have privileges on the environment's data.
- If the environment has a Common Data Service database, a user must be assigned the System Administrator role instead of the Environment Admin role for full admin privileges, as described in the preceding table.
To regulate the administration of creating new environment itself is different. Read this