Answered

User Read/access rights error when triggering Power automate flow from power apps

(0) Share

Report

Posted on by CU08032320-0

I have recently included a feature in a working power app to trigger a automate flows. The app is part of a solution which the power automate flow is also included. I export it as a managed solution to the production environment. I am able to trigger the power automate flow from the app with no issues. However when other users try to trigger the flow from power app they get the User with ID XXXXX doesn't have read access rights for record with ID xxxxxx of entity process.

I've tried the following

1. connections in power flow as run only user and run with my connection

2. Adding and removing the flow from the app.

3. Confirmed when the user tries to run the flow its not even triggered and shows no failure in the power automate run history

4. Users already have read right access to all sharepoint list and the app currently patches fine with their credentials.

5. The flows are Get,Creating and Create document actions in sharepoint using my credentatials

I work for a company and am keen on not trying any change user access requirements until absolutely necessary or a serivce account. Its really strange that power app and power automate dont seem to work well went deployed in a solution. any tips on how I can get around this issue as Im keen on including more automate flows in the future.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Suggested answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@CU08032320-0,

User with ID XXXXX doesn’t have Read access rights for record with ID YYYYY of entity process
When a Power Apps button triggers a flow, Power Apps first checks: the current user have read access to the flow definition?

If the user cannot read the flow record, Power Apps never even tries to trigger it, which is why:

No run appears in Flow run history

No SharePoint permission issues

Works perfectly for you (creator/owner)

Fails for everyone else

The issue is not because of the sharepoint permission / Run‑only user configuration /Connection reference issue.

It is Dataverse security on the Flow (Process) record itself.

Create a minimal custom security role & Assign this role to users who use the app or Use an existing role Environment Maker /Basic User.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@CU08032320-0,

A quick follow-up to see, does the suggestion worked for you or still you were looking for any other approaches or assistance.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
Verified answer

deepakmehta13a 369 on at

Like
a
(0)

Report
Copy link

Link copied!
Hello,
The error regarding 'Read access rights for entity process' is a classic Dataverse security role hurdle that occurs specifically with Solution-aware flows.
To fix this, you need to ensure the Security Role assigned to your users has the correct permissions for the Process table:

Locate the Table: In the Power Platform Admin Center, edit the Security Role assigned to your users.

Go to Customization: Navigate to the Customization tab (this is where the 'Process' entity lives).

Set Permissions: Find the Process table and ensure the Read permission is set to Organization level.

Sync the App: Ensure that when you 'Share' the app, you are sharing it with the same Security Role that now includes this 'Process' read access.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated

Was this reply helpful? Yes No