Power App based flow is giving error

(1) Share

Report

Posted on by MS.Ragavendar

6,274 Super User 2026 Season 1

Power Apps Triggered flow is working for few user but not working for other users getting this error.

Data Source - SharePoint (No Premium Connector Used)

Since it mentioned access level error with the Business Unit I checked he is having the Basic User as part of Environment.

Can anyone share the ideas.

Categories:

Building Power Apps

Error handling

General topics

I have the same question (0)

All responses (9)

Answers (1)

Fredrik_A 3,566 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey,

have you associated the flow with the app?

Associate flows with apps - Power Automate | Microsoft Learn

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
Suggested answer

Power Platform 1919 2,205 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @MS.Ragavendar,
can you please try assigning "App opener" role to the end users and test?
The App Opener role will grant access permission to Process (System) table.

Was this reply helpful? Yes No
Suggested answer

DP_Prabh 331 on at

Like (0)

Report
Copy link

Link copied!

Hi @MS.Ragavendar,

The error in your screenshot says essentially: user doesnt have readAcess for record of entity Process. I think you should assign basic user at least read access on Process table in Dataverse.

Check these settings:

1. Check Process table permissions
If you want to keep the Basic User role: Edit the role > Go to show all tables > Find Process table > Give at least Read (Business Unit level) and append permission.

2. Check Flow Run-only permissions

- Open the Power Automate flow
- Click Run only users
- Ensure users are added and using the correct connection.

I hope this works for you!

Was this reply helpful? Yes No
Suggested answer

11manish 769 on at

Like (0)

Report
Copy link

Link copied!

The error 0x80048306 specifically states the user does not have ReadAccess for a record of entity Process. In Dataverse, "Process" is the table that stores Power Automate flows.

Even though you aren't using "Premium" connectors for SharePoint, the act of a Power App triggering a flow requires the user to have permission to "read" and "invoke" that flow object within the environment's Dataverse metadata.

Was this reply helpful? Yes No
Suggested answer

Kalathiya 1,669 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @MS.Ragavendar,

Try to create a custom security role, giving the user Read access on the Process entity and assigning it to affected users. Could you please test this? I think it will fix your issue.

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Mention @Kalathiya anytime!
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helping!

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

Like (0)

Report
Copy link

Link copied!

@Fredrik_A , thanks for the response I don't think so there is an issue because of the association since we are adding the powerapps based flow right?

@Kalathiya, thanks for the response, With the Basic User itself having relevant permission to the process table so why there is need for custom security role ?

@Power Platform 1919, thanks for the responses let me try to update with this 'App opener' and revert you back.

@DP_Prabh, thanks for the response if you provide solution with the help of AI please select Mark Reply as AI Assisted.

Was this reply helpful? Yes No
Kalathiya 1,669 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hello @MS.Ragavendar,.

I’ve faced a similar issue before. As per my understanding, even though the Basic User role includes permission for the Process entity, the access level is usually User level, which means a user can only read records they own.

If the flow/process is owned by another user or service account, other users may not have access, which can cause the ReadAccess error.

It seems the affected users only have User-level access, not Business Unit or Organization-level access. Could you try giving them Read permission on the Process entity at Business Unit or Organization level?

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

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

Like (0)

Report
Copy link

Link copied!

@Kalathiya, thanks for the response tried with custom role and update the permission for the entity no changes.

@Power Platform 1919 also tried your suggestion still on the same boat.

We tested with same solution in different environment without custom role / role updates with the basic user itself its working. Couldn't able to break the nutshell hence raised a support ticket with MS on this note.

Thanks @Power Platform 1919 and @Kalathiya for the support

Was this reply helpful? Yes No
Verified answer

MS.Ragavendar 6,274 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

The association details of the environment have been flushed and system tables have been updated in the environment by MS Team which helps in resolving the issue.

Was this reply helpful? Yes No