Column-level security - what is the implementation approach to cater for unrestricted and restricted users

Question & Answer
, , ,
1

I have a HR dataset - empId, empName, dept, joinDate, rank, salary (simplified version).
salary is restricted to certain users.

As per this document Using column-level security to restrict access to a dataset - Amazon QuickSight, most visuals having restricted columns that you don’t have access to, you can’t see the visual in your analysis or dashboard.

Does this mean that I need to have 2 separate analysis - 1 for restricted users and 1 for non-restricted users? Which I think is inefficient way of development and maintenance. What is the optimal approach then?

Thanks!

2

Hello lbl,

Thanks for reaching out.

You don’t need to create two separate analyses for restricted and non-restricted users in Amazon QuickSight . Instead, you can use a single analysis with carefully designed visuals that either avoid using the restricted salary column or use it only in specific ways (e.g Table and Pivot Table ) that maintain visibility for all users while respecting column-level security (CLS) permissions.

Regards,