Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi everyone,
I am fairly new to PowerBI Service and I am kinda stuck on a problem. Here is the issue:
I have a PowerBI App which is made up of two different reports; Report A and Report B.
I want Report A to be visible by anyone in the organization but Report B only visible to a restricted list or group of people.
I would want that two level restriction scenario to live in the one PowerBI App.
Is that possible? Or is there any workaround.... at the moment, it seems that Report B keep inheriting the security from the App..
Thank you so much for your help
Solved! Go to Solution.
Hi @Anonymous ,
In a single power bi app, it is for anyone who has access to it. In other words, if someone who has access to visit this app, he can see all the reports except those that were hidden when the app was published in navigation page.
So if you want to restrict some users to see part of reports while others can see all reports in the same app, I'm afraid it is not supported in power bi service currently.
What we can achieve is to restrict users to see the data in the report by using row-level-security. Please refer this document: Row-level security (RLS) with Power BI
Best Regards,
Yingjie Li
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
@Anonymous I know this is a closed question, but what did you end up doing? Did you create a separate Workspace or did you implement RLS on each report?
I'm having the same exact issue right now. My problem would be solved if Power BI would allow for rights at the report level to be set within an App. I don't want to create a separate App or deal with RLS.
Let me know what you ended up doing.
Hi there!
So essentially what I did for this was, I created two separate reports. (A & B). Report A was my main one and also acted as my landing page. I essentially put a note and hyperlink to Report B from Report A. Report B lived in its own workspace with its own set of access rules. It was not the perfect solution but it did the job!
OK, thanks. I was hoping not to have to create a separate Workspace to handle this. I think I will submit this as a feature request.
You can create two buttons for each report bookmakrs. if user have only permission to Report A, hide both Tabs (make them transparent using DAX) and default to report A bookmark. If user have access to both reports, show both buttons to switch between reports.
Hi @Anonymous ,
In a single power bi app, it is for anyone who has access to it. In other words, if someone who has access to visit this app, he can see all the reports except those that were hidden when the app was published in navigation page.
So if you want to restrict some users to see part of reports while others can see all reports in the same app, I'm afraid it is not supported in power bi service currently.
What we can achieve is to restrict users to see the data in the report by using row-level-security. Please refer this document: Row-level security (RLS) with Power BI
Best Regards,
Yingjie Li
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
it is technically possible, by implementing RLS for Report B. But it will also lead to a bad user experience - lots of "you don't have access to the data in this visual" messages that are infuriating to users.
Better solution is to create a separate workspace for Report B. You can still re-use the dataset, but now you can have different access controls.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
56 | |
28 | |
25 | |
22 | |
20 |
User | Count |
---|---|
63 | |
48 | |
24 | |
24 | |
17 |