1. Microsoft Learn
Power Platform documentation
"The default environment."
Section: "Environment Maker role in the default environment"
Content: "By default
all users in your tenant have the Environment Maker role in the default environment... Because the Environment Maker role is the default in the default environment
admins should consider if they want to keep this assignment." This directly confirms that users can create apps in the default environment without any admin intervention.
2. Microsoft Learn
Power Platform documentation
"Environments overview."
Section: "The default environment"
Content: "There's one default environment for each tenant
which is shared by all users in that tenant... Whenever a new user signs up for Power Apps
they're automatically added to the Maker role of the default environment." This explains the automatic nature of permissions in the default environment.
3. Microsoft Learn
Power Platform documentation
"Control user access to environments: security groups and licenses."
Section: "Restrict access to an environment"
Content: "If you don't associate a security group with an environment
all users with a Dataverse license... will be able to access the environment." However
it clarifies that for non-default environments
an admin must still assign security roles. The default environment is the only one where the Environment Maker role is assigned automatically to all users. This highlights the restricted nature of production and sandbox environments compared to the default one.