How to restrict access to a column from a table?

[Li_Yang]

Is it possible to give access to a specific user for a column of a table? I would like only give access of the column “DT” to some specific users and everyone can view rest of columns in the table. I tried the function " Column-level security", but the whole table is restricted.

Survey Sample

[apjvinod]

Hi @Li_Yang

yes with QuickSight Column level security you should be able to restrict access to a specific list of users for certain columns in a dataset . Please follow the instruction and sample dashboard in the below Democentral page.

https://democentral.learnquicksight.online/#Dashboard-FeatureDemo-Security-CLS

Did this solution work for you? I am marking this as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community Q&A Forum!

Thanks
VInod

[Li_Yang]

Hi @apjvinod,

Thanks for your quick response. When I applied the column level security just for one column, but the table is restricted, no one can see the table.

I expect everyone can see the table without the restricted column, but only users have access to the specific column who can view the table with the restricted column. Is it possible?

[apjvinod]

Hi @Li_Yang

Currently If any of the CLS restricted fields used as dimension (group by section) in the visuals then the visual will be rendered only for the authorised users . It will be wrong to do LAC calculations if any intermediate attribute is restricted for a user .

If there is no aggregation required then you may keep all the attributes in the values section of Table visual and all the user will be able to see the visual along with restricted column without any values .

Did this solution work for you? I am marking this as, “Solution,” and “Feature Request” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community Q&A Forum!

Thanks
VInod

[Li_Yang]

@apjvinod

Currently If any of the CLS restricted fields used as dimension (group by section) in the visuals then the visual will be rendered only for the authorised users . It will be wrong to do LAC calculations if any intermediate attribute is restricted for a user .

If there is no aggregation required then you may keep all the attributes in the values section of Table visual and all the user will be able to see the visual along with restricted column without any values .

Hi @apjvinod , Thanks for your suggestion. When I use the regular table visual , and locate the restricted column- dt_login_f in “group by”, the whole table is restricted. If I locate dt_login_f in the “value”, it aggregates with count automatically. Is there any way to not aggregate dt_login_f ?