Forum Discussion
Power Bi Apps - Paginated Report Access Issue
Hello bdpr_95 ,
Thank you for sharing the screenshot it was helpful in identifying the issue.
In Power BI Apps, paginated reports are handled differently than standard reports. Even if users are included in the app audience, they still need direct permission on the dataset to access paginated reports.
To resolve this:
To grant your users access to the paginated report, open the workspace where both the report and dataset are located. Find the dataset used by the report, click the three dots (…), and choose Manage Permissions. You can then add the necessary users or audience group, making sure to give them either Viewer or Build access.
After completing these steps, users should be able to load the report without connection errors.
If you need assistance reviewing the setup, please let me know.
Regards,
Community Support Team.
Hello bdpr_95 ,
Thank you for sharing the screenshot it was helpful in identifying the issue.
In Power BI Apps, paginated reports are handled differently than standard reports. Even if users are included in the app audience, they still need direct permission on the dataset to access paginated reports.
To resolve this:
To grant your users access to the paginated report, open the workspace where both the report and dataset are located. Find the dataset used by the report, click the three dots (…), and choose Manage Permissions. You can then add the necessary users or audience group, making sure to give them either Viewer or Build access.
After completing these steps, users should be able to load the report without connection errors.
If you need assistance reviewing the setup, please let me know.
Regards,
Community Support Team.
Hi V-yubandi-msft, unfortunately giving read access doesn’t work. I have an Azure group, and I’ve already added that group both to the semantic model and to the corresponding audience of my Power BI app.
Hi V-yubandi-msft, I asked the end user to test again (without making any changes) and it's now working fine.
Thanks!