Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Fabric Ideas just got better! New features, better search, and direct team engagement. Learn more

Security - Ability to maintain source security for reports published on BI Sites

The general requirement is that visualizations (Power View, SSRS etc...) must not circumvent existing policies, or introduce yet another set of security policies on top of those already implemented at the source. * For example, a visualization of sales data needs to reflect the policy that account managers can only read sales data for their region. * For performance reasons, this is enforced at the source by injecting predicates into the query based on the end users identity. If identities for end users are not passed down the process chain into the data layer, it leaves us little option but to publish individual reports for every region, which results in an explosion of complexity and numbers of reports, or move the whole model to BISM and manage the policy in yet another place (namely the BISM model). Impact blocking migration to SPO/BI Sites. At least 412 Site Collections with more than 600 Power Views. Impacting Adoption or migration for majority of BPUs - e.g. Finance, LCA, HR, etc
Status: Under Review
Comments
datauduong
New Member
We have 1 common data source where we want to be able to show certain data based who is viewing the report, is this currently possible to do ?
datauduong
New Member
Am I understand this correctly that, it is an ability to link Logged in User to the Rows Level Data that the User Can see ? That's what I want to do now.
vivek_bheda
New Member
Please add this functionality as there is always requirement for sales firm to show saleperson user their own data when they logged in to office 365 tenat. We should be able to write a query that allow us to filter data with the current user logged in
vivekdevalkar
New Member
This is one of those "deal-breaker" kind of features that will determine whether one can use Power BI or not. Absolutely has to be on the immediate roadmap for Power BI.
vivekdevalkar
New Member
This is one of those "deal-breaker" kind of features that will determine whether one can use Power BI or not. Absolutely has to be on the immediate roadmap for Power BI.
kim_ming_chan
New Member
We are creating dashboards which must be used by multiple clients. But the client must only sees his/her data, the data is loaded via Azure SQL Database. So a kind of row level security must be available. What can we expect to enable this functionality?
venu_sura
New Member
it will very useful we if get the Row based security with in the Power BI
Rory3
New Member
Adding row-level security within Power BI would be fantastic. At the moment dax rules could be applied via ssms locally to the designer file. Do these carry over when the designer file is loaded? Even if that was supported it would be something.
derksl
New Member
I would also love to see row-level security within Power BI. I'm used to creating row/role based security in a tabular model.
Michael_Johnso5
New Member
Much needed. Waiting on this feature before implementing Power BI as part of our company information system. In my opinion. PowerBi should not be considered an enterprise application without the ability to filter data based on the logged in user.