Answered

Principal user is missing prvReadWorkflow privilege on OTC=4703 for entity 'workflow'

(0) Share

Report

Posted on by nok

Hi,

I have two flows that run from PowerApps. For some users, these two flows work correctly, but for others, neither flow works and the following message appears:

I've already added user groups that can access Automate in the "Run only users" panel of both flows, but these flows still don't work for some people. Both flows are not even triggered.

Does anyone know how to fix this?

Categories:

Building flows

I have the same question (7)

All responses (5)

Answers (1)

stampcoin 5,060 Super User 2025 Season 2 on at

Like (1)

Report
Copy link

Link copied!

@nok Hi,

Glad to hear that.😊

My suggest is that create a M365security group and associate it to the environment.

If you don't want to create another security group, you can create a power automate flow to sync users.

For example.

Was this reply helpful? Yes No
nok 38 on at

Like (1)

Report
Copy link

Link copied!

@stampcoin, Hi!

Now it works! After inserting the user into the same Security Role as you mentioned, I went to the Users screen, selected the users who were having trouble running the automate, and clicked "Update User" in the top menu. After that, the users were able to run Automate :)

Thank you very much for the solution!

I'll mark your answer as the one that fixed the problem. I just have one last question after this whole Security Role issue... how do I make this app accessible to anyone in the company? Do I always need to add users to the same access groups as I'm adding now? I want anyone in the company to be able to use the app (and its flows), without me having to keep adding them to the environment's Security Roles.

1 people found this reply helpful.

Was this reply helpful? Yes No
stampcoin 5,060 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

@nok Hi,

thanks for the feedback.

Do they belong to different business unit ? Did the basic user

There should be something security difference caused this.

Was this reply helpful? Yes No
nok 38 on at

Like (0)

Report
Copy link

Link copied!

Hi @stampcoin, Thanks for the quick reply!

I found the screen you mentioned, with the Customization tab and the Process row, but in my case, the users are in the same Security Role. Both users who can't run the Automate and users who can run the Automate are in the "Basic Users" Security Role.

Even selecting users individually on the "Users" screen shows that they belong to the "Basic Users" Role.

So, is there anything else I need to do after the users are in the same Security Roles?

Was this reply helpful? Yes No
Verified answer

stampcoin 5,060 Super User 2025 Season 2 on at

Like (2)

Report
Copy link

Link copied!

@nok Hi,

Those users don't have enough access right to process.

see below article refers

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/reference/similarityrule?view=dataverse-latest

Go to https://admin.powerplatform.microsoft.com and select the correct environment, go to Settings,

Under Users + permissions, click Security roles.

Check the users' who don't have access right, and compare the one who can run the flows.

make sure those users have the same role ( add those users to the ones who have access)

if they cannot have the same security roles, create a new one for those users (who cannot). and make sure they have the read access to the Process.

below screen shot if only for your reference.

Was this reply helpful? Yes No