Piyush Dhameja on 14 Sep 2016 13:09:18
Add security to show/hide any specific page (Tab) on a report based on users privileges / Roles.
Administrator on 18 Apr 2024 09:59:22
Thanks for all the feedback! Currently, Power BI does not have a security feature for pages; however, using conditional page navigation and RLS, you can create a custom navigation experience that shows different page options for different roles.
- Comments (614)
- Merged Idea (8)
RE: Page (Tab) level Security.
A workaround is not a solution. Please make it happened
RE: Page (Tab) level Security.
A button to navigate is often not a solution. If it is a one page report that few extra or less fields/visuals, we really need it to just load, especially if it is for access for top management or factory floor supervisors. They don't want to have the extra click. Just load the correct page.
RE: Page (Tab) level Security.
when Microsoft will provide this feature ??
it"s definitely a MUST HAVE !!
RE: Page (Tab) level Security.
We need a 'REAL' Page Level Security feature. I am pretty sure many people will love it.
RE: Page (Tab) level Security.
We need this fix ASAP! @Microsoft
RE: Page (Tab) level Security.
I have achieved this using RLS and Page navigation. I did the RLS for Product names in table then took same product as the Navigation. Now it shows only the products assigned to the particular users...
RE: Page (Tab) level Security.
I hope that "Under Review" is a good sign. This is a really important feature that I'm sure will be very popular. The workaround that you posted is easily hackable. When you're dealing with Sales people and commission info, security should be the priority. In my report, I already have RLS security set up and only those salespeople assigned to certain regions can see their regions. That's good. However, there are pages that don't apply to them and it's a big issue having to create 2 separate reports. That doubles the maintenance!
RE: Page (Tab) level Security.
What is so terribly hard about this? At a basic level, the only functional improvement that needs to be added is to enhance the Permissions model at the page level. This allows for the existing Report/App level permissions to remain, and within that permission scope each page can be assigned specific permissions, with the report/app level scope set as the default.
This doesn't require any changes to the existing RLS model, so that a page that has RLS continues to work as currently implemented.
This model would also keep the same security context whenever a report is exported to PPT, PDF or Analyzed in Excel.
RE: Page (Tab) level Security.
Omar como solucionaste este tema?
Gracias
Leo A
RE: Page (Tab) level Security.
Please do consider below point before doing a public preview.
1. If report has “REPORT BOOKMARKS” user can still bypass the page navigation and access the pages. – Please give report authors to hike the “REPORT BOOKMARKS”.
2. Export to “PPT” – user can still bypass the page navigation and access the information.
3. Export to “PDF” – user can still bypass the page navigation and access the information.
So, we need a proper Page security so we can use single report/App for different department with Page security. Thanks