Power Platform Community Forum Thread Details

Hello,

I have two custom security roles that were deployed from my development to production environment, however they are not working in said production environment. The key difference between the two is Role 1 has create access to some table while Role 2 does not. I have checked the following things in trying to figure out while all but one user is able to open the application:

The users exist in the environment & Dataverse table. - they do.
Checked the environment settings for users, roles, column security, organization. - everything matches between production and development environments.
The roles are assigned to the application. - they are.
The application is shared with the users and their roles are assigned. - it is and they are.
The users are added to their column security roles. - they are.
The users are checked in the app access checker. - They were, the single user that can open the application has visibility = Yes, License = Yes, and Security = Yes, but if I were to assign the same role to a different user only the security = Yes.

I have attempted to remove the role from the application, publish it, readd, republish, and reshare with the other users and there is still no luck. All users I have shared the application with do have licenses this has been confirmed, but the visibility for all but the one is still equal to no.

I have tested these roles in the development environment with the same users I've been trying to use in the production environment and they work perfectly fine in development.

How do I turn on visibility for other users? Why would it only work for one person that isn't an admin? Why would the roles work in development but not in production after being deployed on the pipeline? Why does it seem like the app opener role does nothing?

Please help I'm so confused.

Thank you

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Microsoft Dataverse with Power Apps

Building Power Apps

Given that:

The roles work in Dev.
Security = Yes.
Visibility = No.
One non-admin user works.

The most likely causes are:

Model-Driven App role assignment issue in Production (highest probability).
Business Unit-specific role mismatch.
Environment Security Group membership issue.
Security cache not refreshed after deployment.

Recommended Next Test

Assign System Administrator temporarily to one affected user.
If Visibility immediately becomes Yes and the app opens, focus on the app role assignments and Business Unit role instances.
If Visibility remains No, investigate the environment security group and app sharing configuration.

The fact that App Access Checker shows Security = Yes but Visibility = No strongly suggests the problem is with app visibility configuration rather than table permissions.