web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / 0x80048306 ReadAccess ...
Power Apps
Suggested Answer

0x80048306 ReadAccess error on Dataverse Process (Workflow) from Power Automate

(0) ShareShare
ReportReport
Posted on by 505 Moderator

Hi everyone,

I'm posting this in the Power Apps forum because the error surfaces when the flow is triggered from a Power Apps app. Even though the failure comes from Power Automate, the issue only becomes visible when the flow is called from the app.

If this is not the most appropriate subforum, please feel free to move the thread or let me know and I can repost it in a more suitable place.

I'm running into a permission issue in Dataverse when a Power Automate flow interacts with the Process (Workflow) table, and I'm trying to understand if something has recently changed in Microsoft’s security model.

The flow fails with this error:

{"error":{"code":"0x80048306","message":"user with id <USER_GUID> does not have ReadAccess right(s) for record with id <PROCESS_GUID> of entity Process."}}

What makes this interesting is that this is the second time I've seen this exact issue in two completely different tenants/clients, both involving the workflow/process table.

 

What I'm trying to understand:

  1. Has Microsoft changed anything recently regarding permissions or access to the Process (Workflow) table in Dataverse?
  2. Are there special security constraints around reading specific workflow records?
  3. Could this be related to solution-managed workflows, ownership, or Business Unit scope?

Since this has now happened in two different environments, I'm wondering if this might be related to a platform change or new restriction rather than just a configuration issue.

Has anyone else experienced something similar recently?

Thanks!

image.png
I have the same question (0)
  • Suggested answer
    BCBuizer Profile Picture
    22,563 Super User 2026 Season 1 on at
     
    This issue is most likely caused by the fact that the Basic User security role only has User level read access to the Process table: 
     
     
    Try cloning the Basic User security role, changing the scope from User to Organization and then assign the role to the users.
     
    In case you are using custom security roles, consider making the suggested change to those instead of the (clone of the) Basic User role.
     
     
    If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 76 Most Valuable Professional

#2
Haque Profile Picture

Haque 69

#3
Kalathiya Profile Picture

Kalathiya 38 Super User 2026 Season 1

Last 30 days Overall leaderboard