In Power Apps, security roles are a foundational part of how users interact with data, views, and forms. However, the current app development experience treats security roles as a separate, post-design configuration — which often leads to confusion, misaligned access, and unintended exposure of system views and forms.

I propose that security role planning be integrated as a mandatory step during app development, especially in model-driven apps. This could include:

• A guided step in the App Designer to define or assign security roles based on user personas
• Warnings or prompts when views/forms are included in the app but not properly secured
• A preview mode to test the app as a user with a specific role
• Better visibility into which roles can access which components of the app

This would help makers design apps that are secure, user-specific, and aligned with business requirements — without needing to troubleshoot access issues after deployment.

Why This Matters:

• Prevents users from seeing unintended system views/forms
• Reduces post-deployment issues and support tickets
• Encourages better alignment between app design and security
• Makes the platform more intuitive for citizen developers

Thank you for considering this improvement — it would make a big difference in building secure, role-aware apps from the start.