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
kirk_potter
New Member
DAX has a USERNAME () function which may help
mstefancik
Advocate IV
Any news?
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
darren_mclean
New Member
Yep, agree with other comments. This would make life so much easier.
javier_recasen2
New Member
Please, we need to manage security in the report itself. Inside a data model, define row security per user.
falcon16c
New Member
I have role in tabular model but in power bi site it's not working in bi desktop it work great somebody can explain
james_gifford
New Member
Agreed! This is definitely needed
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?
bassbr2002
New Member
If we were to dynamically display/secure data, it would be interesting to have the current user logged in expose to the interface
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.