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
Ideas Administrator

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

So yes, now you can make a certain column unavailable for a certain role. But then the end user, with this role, just sees an error in all the visuales where the column is used.

In my opinion the goal would be to then show the user at least all the other columns he is allowed to see. Without any error or warning.

Since this is currently not the case and you have to use external tools, I would suggest to keep this topic as not yet solved.

T

Hello,
Will this feature will be released this month or was postponed to March ?

T

It would be a game changer in BI industry, we need this ASAP.

T

This would be a very welcome feature.

T

Can we please get this feature implemented as it has been a long wait for Customers like us. A much-needed security feature when doing reports on sensitive data across the Business Verticals.

T

I hope this gets more votes; We need this desperately or at least the ability to do composite models with AAS.

T

If not outright column-level security, at least allow a function to "preserve" RLS. If I can preserve the current user as filtered by RLS, I can create a DAX calculation that can show or hide the values in a column. Not perfect, but a start... the need in our business for this, is critical.

T

Wouldn't be page level security more useful?

https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/40467436-page-tab-level-secuirty

T

This is vital in terms of efficiency of reporting with regard to maintenance and upkeep of reports.

For example let say you have columns, 1 for invoice numbers, 1 for amounts and a 3rd for line item details.

We might want certain people not to be able to see the line item detail as it may contain sensitive information but cannot ensure that only specific users can drill down to this detail.

Currently this means running multiple reports for different user groups. In most of our uses cases where data sensitivity is a factor CLS has considerably more applications than RLS, which we hardly ever use.

T

If I could even access the user role via a DAX switch statement, that would be enough for what I am trying to do.