2

In powerapps admin centre, I have an environment without CDS.

Inside the environment there are 2 roles - Admin and maker. Is it environment admin and environment maker? Or is it powerapp admin and powerapp maker?

What permissions does user need to create and use powerapp?

variable
  • 8,262
  • 9
  • 95
  • 215

2 Answers2

0

Inside the environment, you can configure the environment admin and the environment maker. enter image description hereDepending on the environment type, your environment maker role can have 1 or more persons associated. The environment maker has enough permissions to create and use resources inside the environment.

An environment maker has the ability to create new resources in an environment. Add or remove people from the Environment Maker security role.

Hugo Barona
  • 1,303
  • 9
  • 21
0

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

  • 1
    As soon as CDS is added to environment, the admin and maker roles no longer exist. And security is controlled by CDS roles. Am I right? Suppose I had the users configured when there was no CDS in the environment. And then later suppose I add CDS to the environment, then does the previous config gets destroyed? Or do they flow into the admin/maker roles that are also provided by CDS roles. – variable May 16 '20 at 15:14
  • @variable great question. But I never tested it. This link talks about that two scenarios in point 3 and 4 but not about the switchover. https://learn.microsoft.com/en-us/power-platform/admin/environments-administration#manage-security-for-your-environments – Arun Vinoth-Precog Tech - MVP May 16 '20 at 15:22
  • @variable I believe only Env admin will go away but still Env Maker will stay as is. Probably all admins has to be given Sys admin if they lose it (I don’t think that’s the case) – Arun Vinoth-Precog Tech - MVP May 16 '20 at 15:29
  • @variable, of special note is that CDS will be **automatically** added to environments in some cases. If a user selects "Model driven app", CDS will be added. If a user creates a Flow with Approvals, CDS will be added. AFAIK, there is no way to turn these off. I've been told that sometime in the future, all PowerApps environments will be provisioned with CDS and this will be a moot point. – SeaDude May 18 '20 at 06:17