Page (Tab) level Security.

RE: Page (Tab) level Security.

I have used the workaround suggested by the administrator, but our issue is that this solution is not very user friendly. Despite trying to highlight the dropdown as much as possible, some of our users still miss the dropdown and end up thinking the report is not working. What would be great is if the Page Navigator feature (Insert>Buttons>Navigator) could link to RLS / be conditional, so that only the relevant pages were displayed as buttons (i.e. if a page was not relevant for a user, it would disappear dynamically from the page navigator). By also removing the need for a GO button, this would minimise user confusion and reduce the number of clicks they need to perform to navigate across a report.

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

RE: Page (Tab) level Security.

Same data set -- but I have to publish 4 different power bi reports because we don't have page level security. RLS only solves what data the user is exposed to. I want to restrict who sees the page.

RE: Page (Tab) level Security.

i (and many others I am sure) would like to hide pages based on users logging into a report with many pages.



Really, really need this soon :(

RE: Page (Tab) level Security.

row level security makes it hard to hide EVERYTHING from a specific client as the data model would be too complicated to structure for RLS to be applied to entire report.

so if there is a way to add security on a per page basis, that would be great.

RE: Page (Tab) level Security.

Managing roles should also be on pages level, not only on tables level. admin should be able to control pages that different users can see based on their assigned roles.

RE: Page (Tab) level Security.

In a Power BI report, hide or show certain pages based on the logged in user.

Maybe use user roles.

This makes it possible to use the same report for several profiles.

RE: Page (Tab) level Security.

The idea is to add in the authorization roles the option to show or hide sheets according to the permissions assigned to the user. This option is very useful and will allow to show different sheets according to the role assigned to each user.

RE: Page (Tab) level Security.

This kind of :

PLS ( page level security ) ?

VLS ( visual level security ) ?

Is really needed, if this is developed it would increase 1000 fold the user experience for the end user, which should be what BI is all about.

Please implement this Microsoft, thanks

RE: Page (Tab) level Security.

RLS ( Done )

PLS ( page level security ) ?

VLS ( visual level security ) ?