2651
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
Needs Votes

Comments

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.

T

Great idea.. 1 report multiple purpose.. thanks for giving the idea..

T

Extremely important and useful facture for the business area.

T

There is no option to apply column-level security. Kindly provide the option where one column is visible to one user while it is hidden for other user

T

Field Level Security:
making one report for everyone, but hiding fields (columns) for some security groups. Today the workaround of building multiple reports on the same dataset is difficult and time-consuming to maintain.

T

It is unbelievable how this feature is still missing in PBI: please add it asap. We are waiting for years now

T

This is a high demand feature and a reason we go with AAS or SSAS instead of a full Power BI based solution.

Could you at least provide an ETA on this, please?