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

Super important functionality and a big gap today. We need this NOW. You got to deliver this functionality ASAP.

T

This would be awesome. Having to run a number of completely duplicated reports just for the sake of two columns, not at all efficient.

T

Something we need it badly in out report, why do Power BI have half baked solutions?

T

This would be a great feature to have.

T

Very much needed. Please add it.

T

Very much needed functionality. Also needs to be able to handle DQ sources when the column is restricted by the underlying source system if at all possible.

T

The lack of this feature has a truly negative effect on our modeling abilities. We are forced to pull columns with a 1:1 cardinality into separate tables just to prevent users groups of users from viewing the data. We absolutely need the ability to prevent users from viewing data in specific columns if not part of a specific security group. This security should also automatically extend to any calculated tables which reference said columns.

T

As said before me, it would be a very nice feature to have in az enterprise setting!

T

I can’t believe this has been over 2 years - massive naively, I would have thought this to be a relatively simple implementation. Equally I can’t believe only 700 off people have voted for this! I would have thought loads more would be after this

T

A Must have feature RLS is great but not enough as we need to limit the measure for some users