Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
We're looking for solutions to implement page-level security within Power BI apps, as the platform currently only supports report-level permissions through app audiences.
Power BI apps allow us to control which reports different user groups can access, but there's no native way to control access to specific pages within a single report. This means we either need to create separate reports for different audiences (which leads to duplicated content), or give users access to all pages in a report (which risks over-permissioning).
To work around this, we've implemented a solution using Row-Level Security (RLS) roles, bookmarks for different page views, conditional visibility on navigation elements, and DAX measures to control what users can see.
While this approach works functionally, it leads to a poor user experience. Users cannot see all available pages in the left navigation pane and must instead navigate through bookmarks embedded within pages. This creates a non-intuitive navigation experience that often confuses end users.
Has anyone found a better workaround that allows us to (1) maintain all page tabs visible in the left navigation pane, (2) implement page-level access control, and (3) keep everything within a single report/app to avoid duplication?
Thanks in advance!
Martina Cahya Pratiwi
Business Intelligence Analyst
Solved! Go to Solution.
Hi @martinacahya I don’t think currently this is supported natively in Power BI — page-level security isn’t available out of the box. While your workaround using RLS, bookmarks, and conditional navigation is a valid solution, it does affect usability. The alternative is to split reports by audience and use a shared dataset to avoid duplication.
Hi @martinacahya,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you are trying to implement page-level security within a single Power BI report published through an app. Power BI currently only allows report-level access control via app audiences, meaning they can assign different user groups access to different reports, but not to individual pages within the same report.
As @Akash_Varuna has already mentioned that at this time, Power BI does not support native page-level security
access control is only enforceable at the report level through app audiences or dataset level using RLS. Kindly go through hsi response and check if it answers your query.
I would also take a moment to thank @Akash_Varuna, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Hi @martinacahya,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well.
And if you're still looking for guidance, feel free to give us an update, we’re here for you.
Best Regards,
Hammad.
Hi @martinacahya I don’t think currently this is supported natively in Power BI — page-level security isn’t available out of the box. While your workaround using RLS, bookmarks, and conditional navigation is a valid solution, it does affect usability. The alternative is to split reports by audience and use a shared dataset to avoid duplication.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!