2950
Ability to define rules at column level, to control the data fields available to different roles (e.g. employee salary visible to the users in finance roles only, while other employee details visible to other department roles).
STATUS DETAILS
Completed

Thanks for all your votes! I'm pleased to say this feature is shipping in the February 2021 update: https://docs.microsoft.com/en-us/power-platform-release-plan/2020wave2/power-bi/object-level-security

Comments

T

Power BI visualizations dynamically supporting SSAS Tabular 2017 Column-Level-Security is a must

T

this feature would be very useful for customer facing reports and hierarchies. Not all customers need to see all levels of a hierarchy

T

Column based security is extremely desired. Mainly because workarounds such as "un-pivoting" cant be used, where you have 40-50 columns and millions of rows.

T

Object Level Security is critical for our dashboards. Please add this feature

T

Object level security to show or hide objects in a report would be amazing as well. Specifically for buttons. My specific use case is that id like to have a button available for each role which takes them to a specific report tab relevant to their role.

T

We have subscribers to our data who need to see different columns of data based on their subscription. This would solve our issue.

T

this functionality is essential when dealing with external customers. I already use RLS but need a way to restrict columns. For example we have a hierarchy up to 10 levels but each customer will have a different number of levels relevant to themselves, so we would want to restrict the view to the maximum customers level and below.

T

Please, we need this critical functionality.

T

Row level security can create problem in that the dataset is basically a filtered set and does not have all the data. I can't see why we can't have something like if username () = 'blah blah' then column.visible ?

T

We need this feature as we work with external customers. Please push it to your priority.