They need the role with the prvReadWorkflow privilege

(2) Share

Report

Posted on by Pardha

Hi,

I am having two environments Dev and QA.

Dev is the type Developer where my unmanaged solution exists

QA I am trying to deploy as managed.

My App has takes data and attachments as input. Upon approval of the request the attachment will be added to the library using power automate flows. It is working fine in Development environment.

However I am getting error in QA environment and the flow is failing to initiate with the below error.

The user with the id 5e5d5276....has not been assigned any roles. They need a role with the prvReadWorkflow privilege.

Please find the SS for more details.

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (0)

Prateek1987 6 on at

Like (0)

Report
Copy link

Link copied!

Hi,
I am also getting the same issue, please let me know if you found any resolution.
Best Regards,
Prateek

Was this reply helpful? Yes No
PaulD1 2,914 on at

Like (0)

Report
Copy link

Link copied!

I am having the same issue.
What role is required for prvReadWorkflow privilege?
CoPilot suggests that Basic User does not have this privilege and you need one of the following (but it might be hallucinating as the references it gives don't seem to say this): System Administrator Role, System Customizer Role, Environment Maker Role, Environment Admin Role, Custom Roles.
Seems dumb if you do need such high level privileges just to run a flow that is called from a Power App.

Was this reply helpful? Yes No
Pardha on at

Like (1)

Report
Copy link

Link copied!

Hi Prateek,

I gave basic user access and it worked.

Was this reply helpful? Yes No
PaulD1 2,914 on at

Like (1)

Report
Copy link

Link copied!

So, the issue I was having seems to be related to having renamed a Flow that was called in the Power App and then exporting the solution and importing it into another environment. The warning message we got related to not having a role with permissions for prvReadWorkflow.
Deleting the renamed Flow from the App and adding it back again resolved the problem. We didn't change the user's role (left it as Basic User).
Typical case of the error message not relating to the actual problem.

Was this reply helpful? Yes No
Pardha on at

Like (0)

Report
Copy link

Link copied!

Thank you for sharing details.

Was this reply helpful? Yes No
HansenvomDeich 184 on at

Like (0)

Report
Copy link

Link copied!

Thanks that was helpful

Was this reply helpful? Yes No