Forum Discussion
Paginated Report Users doesn't have acces
Hello,
I need help concerning a paginated report where users can't have access. They can use every reports they have access to (from a link) without any problem, I decided to give them access on a report through the Paginated Reports embedded from Dekstop.
But when they try to access the paginated reports, they can't open it because they doesn't have access.
Even with using the app and with a typical audience, they can't use the embedded paginated report.
Is there a reason, so? What should I do? Do I need to give access to every person that needs to use this with their e-mail ?
Thanks for your response.
A-M
Yes, that behavior is expected. Permissions on the embedded Paginated Report visual are not inherited from the Power BI report that hosts it, so each viewer needs their own access to the paginated report.
At minimum, every user who opens the outer report needs read access to the paginated report itself (through the workspace, direct sharing, or the app). If the paginated report queries a Power BI semantic model, they also need Build permission on that model. For other data sources, either the paginated report's stored credentials will cover the connection or the user's own credentials are used when the data source is set to single sign-on.
The cleanest setup is usually to publish the paginated report, its semantic model, and the hosting Power BI report into the same workspace or app, and grant the users the Viewer role plus Build on the model.
If this helped, a thumbs up and marking it as the solution would be appreciated.
Best regards,
Shai KarmaniHi Nekauli,
You can make this easier by using Entra groups.
Make a group for this report, and grant the group permissions both to the app and to the paginated report.
Then to grant users access, all you need to do is add them to the group.You can also set up automations that will automatically add users to the group based on various conditions using Power Automate.
4 Replies
- Shai_Karmani
Super User
Yes, that behavior is expected. Permissions on the embedded Paginated Report visual are not inherited from the Power BI report that hosts it, so each viewer needs their own access to the paginated report.
At minimum, every user who opens the outer report needs read access to the paginated report itself (through the workspace, direct sharing, or the app). If the paginated report queries a Power BI semantic model, they also need Build permission on that model. For other data sources, either the paginated report's stored credentials will cover the connection or the user's own credentials are used when the data source is set to single sign-on.
The cleanest setup is usually to publish the paginated report, its semantic model, and the hosting Power BI report into the same workspace or app, and grant the users the Viewer role plus Build on the model.
If this helped, a thumbs up and marking it as the solution would be appreciated.
Best regards,
Shai KarmaniThanks for your response!
Is there a more efficient way to grant users access to paginated reports without having to manually enter each user's email address?
I have several paginated reports, each of them being shared with more than 50/75 users, so adding every email address manually is quite time-consuming.
Ideally, I would like to know if there is a way to automatically assign access based on a user list, for example by importing users from a file, using a group, or through another automated method in Power BI.
I also tried granting access through the Power BI app, but unfortunately that did not work as expected.
Is there any recommended approach for managing access at this scale?
- tayloramy
Hi Nekauli,
You can make this easier by using Entra groups.
Make a group for this report, and grant the group permissions both to the app and to the paginated report.
Then to grant users access, all you need to do is add them to the group.You can also set up automations that will automatically add users to the group based on various conditions using Power Automate.
v-achippaCommunity Support
Hi Nekauli,
Thank you for reaching out to Microsoft Fabric Community.
Thank you Shai_Karmani and tayloramy for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
