RBAC Functionality - Field-Level; View-based ACL; prevent displaying sensitive data to the wrong people

“enable admins to block off search/viewing access to certain resources like datasets to groups/individuals” (original post in DH Slack)

“enable admins to block view of sample data values given by profiling runs in Stats view

• Aggregated statistics in Profiling runs should be fine.

• Being able to see column descriptions and all datasets might allow data discovery.

• Being able to see sample data in profiling runs is like people getting access to data that they should not have access to. There could be sensitive info which a team that does not have access should not be able to view. I would rather block everyone from seeing sample values over them accidentally being able to see data that they should not have access to.

We are rolling out datahub to the whole company slowly. But if we had profiling on datahub it would show sample values. This can be a big concern during an external audit. This is one big reason we have not enabled profiling for most of our databases.” (original post in DH Slack)

“from our data teams, ‘technical users have access to more technical data but standard users aren't exposed to the 'flood gates'“ — looking for the ability to turn off data profiling.” (original post in DH Slack)

“Hope that the team can implement view ACLs to restrict view/search to view certain resources down to field level. For instance, we have contractors that require only specific resources for them to proceed with their subsequent work.” (original post in DH Slack)