I only want the end users to access what's in the report, not the entire semantic model.
Today, when sharing a report, we also share read permission to the entire semantic model (except for any RLS or OLS restrictions).
This is unintuitive and risky, because many people are not aware that they actually share the semantic model when sharing a report.
Instead, I only want the end users to access what's in the report, not the entire semantic model.
2 Comments
- frithjof_v
Community Champion
When I say "Today, when sharing a report, we also share read permission to the entire semantic model..." I mean this is what automatically happens, and there is no way around it. This is not something we want. This is just how it works but I don't think it should work like that. It should be optional. - frithjof_v
Community Champion
One example of what I want to get rid of, is the "show data point as a table" mechanism that displays granular data that the report creator didn't intend to display: https://blog.crossjoin.co.uk/2021/11/07/is-power-bis-show-data-point-as-a-table-feature-a-security-hole/
Recent ideas
Enforcing OneLake Security on external semantic model API calls without adding security risks
Problem External applications cannot query Fabric semantic models on a user’s behalf - with OneLake RLS security rules enforced - unless the Fabric API is exposed to any and every client an authoriz...sean_cochran1 hour agoResolver INew17Views0likes0CommentsAllow ownership transfer (“Take over”) for Activator items
Activator rules run under the identity of the item’s creator. When that person leaves the organization and their account is disabled, all rules stop working silently. Unlike other Fabric items, there...ndelcastillo1 hour agoRegular VisitorNew21Views1like0CommentsRestore "no-reply" option for Power BI Subscriptions
Please add a setting in the Power BI Subscription pane to choose the sender identity. With the recent update the platform forces emails to route through the subscription owner's personal Exchange On...LenaFid3 hours agoRegular VisitorNew257Views43likes10CommentsFabric Desktop: A Local Development Experience for Microsoft Fabric
One of the biggest challenges in Microsoft Fabric today is the one branch per workspace limitation, which makes it difficult to work on multiple feature branches simultaneously without creating separ...raym854 hours agoAdvocate INew1.4KViews15likes2Comments