Solution:
No, Auto Insights does not have monitoring functionality to identify fields as PII or other restricted fields. So depending on who has access internally to data and administrator access in Auto Insights, PII or other sensitive organizational data can be uploaded.
What can be done instead?
Create checks and processes into your Auto Insights production upload process in order to prevent sensitive information from being uploaded. One way to do this is to centralize the data upload process to a team or select individuals. You may already have existing teams that are similarly responsible for other processes. What this does is creates a single point of entry where all data to be uploaded into Auto Insights comes through and this team or individuals can check as part of the production process, whether or not sensitive or restricted data is being uploaded. This can also benefit the standardization of data fields and naming convention. Having this centralized group be responsible and implementing your organization's data best practices can enhance the Viewer experience with consistency from dataset to dataset. (additionally if your column naming is consistent across the org, you may be even able to create a Macro in Designer to check the dataset to see if sensitive data is being passed through - an open challenge to anyone in the comments!).
To implement this centralized check, simply give your team or select individuals administrator access and all other users normal Viewer/User license roles and implement the data best practices for your org.
David Kim
Customer Success Manager
Alteryx
