Model Driven Apps (Part 1)
Neil Haddley • September 18, 2023
Setting up users and Dataverse security roles in a Model-Driven Power App — assigning roles to each user based on their duties
The illustration below shows the p8lf organization structure. I assigned Dataverse security roles to each user based on their duties.
Environments
Power Apps environments are logical containers for building, testing, and deploying apps, flows, and solutions. I used them to isolate development from production, manage access, and control deployment across the project lifecycle. I created a Develop environment alongside the default p8lf environment provided by Microsoft.
Solutions
In Power Platform, Solutions are containers for grouping related components — apps, flows, custom connectors — into packages that can be deployed across environments. I used Solutions to organise assets, manage versions, and transport components from the Develop environment to production.
Suggestions
As a demonstration I created a Suggestions model driven app.
The steps are shown below.
Environments and Solutions
The Basic User role grants access to core business tables and lets users run apps and manage their own records. The Environment Maker role lets users create resources — apps, connections, flows — but doesn't grant access to data. Neither role was sufficient for Isaiah to access the Suggestions table or run the app.
Business Units
Lee and Lidia are in the same Manufacturing business unit. As Director of Manufacturing, I wanted Lee to be able to read and manage all suggestions made by anyone in his business unit.

























































