It's necessary to find a native method to hide pages from specific users without having to create two or more different reports. This way, with just one report, different people within the company could see both shared pages and those belonging to specific groups. Currently, there's a non-native method using RLS, but it has several bugs: firstly, page navigation is only possible via a dropdown list, and it doesn't allow for a button menu. Secondly, if someone with permission has left a folder selected in that menu, those without permission can also see what's left, requiring complicated rules to prevent this. After the project is published, if the report is exported to PDF, the hidden pages can be viewed. There's an option to prevent exports, but some clients need these exports. Therefore, this is a key security issue that needs to be resolved. Having three or four identical reports where a page changes to one that certain groups can't see becomes cumbersome, duplicated work, and unnecessary...
Recent ideas
Custom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON1 hour agoNew MemberNew5Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi3 hours agoMicrosoft EmployeeNew20Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull224 hours agoAdvocate INew31Views1like1Comment