Restrict access to report page at user level

[Anonymous]

Hello,

I would like to understand if is there a way to forbid access to a user or group o users to a page of a report. The idea is to be able to publish a single report, and then create a kind of administrator view that only certain users can access.

Thank you very much

[martinmichalsky]

I know this is already closed, but someone could use my guide on how to create navigation and hide some pages via buttons. 
Check my solution here

[MFelix · Accepted solution]

HI @Anonymous,

You can use row-level security (see the link below), but note that this will return a blank page to users will not be hidden, but with the data to filter.

https://docs.microsoft.com/en-us/power-bi/service-admin-rls

[Anonymous]

Dear Miguel,

This approach can confuse the users as they can easily get lost in all the other 20-30 pages that are not relevant to them. Is there no other way?

As much as I have figured out:

Restriction of Access:

- Within a workspace - a person can view only a report he has access to.

- Within a report - a person can view all the pages.

- Through a dashboard - can go back to a report from which it was created.

I have the same query and tried looking for work-arounds but still for a clean way. Need your kind suggestions.

Here's my situation:

- My pbix (hence 1 report) = 20 pages. Published to Service. Put RLS to 10 users. They see all 20 pages but only their data. Some pages have a lot of data that's confidential/irrelevant to them and not restricted by RLS.

Workaround 1

- For each page, I pinned live and created a dashboard.

- On each db, shared to the users.

Result

- Now they see only this db, but have access to go back to the main report, and hence all 20 pages are open again.

- So, wordaround 1 - ineffective.

Workaround 2

- I created individual reports on Service directly from the published dataset. i.e. recreated each of page of the main report as an Individual Report. (1 report = 1 page)

- Shared each report (or the db pinned from that report) with the users.

Result

- Now they can go back only to the individual report (= 1 page) from a db, not to any other report or the main report that 20 pages.

- This seems effective, BUT creating a report on Service is a big problem. Why?:

---- There's no way to backup these reports (I lost all my reports, when our IT admin moved our domain to O365 last week!!)

---- Formatting is very difficult. There's not format painter mainly (and a lot of options) on Service vs. Desktop.

Could you kindly recommend the best practices in this case? Should the reports be created on Service or Desktop?

Thanks,

Vinod