Managing Sensitive Information

Motivation

We recommend enterprise users establish a base account which contains the base versions of datasets that will be distributed and updated to customer accounts. With this setup, enterprise admins can iterate and ensure that these datasets and their data assets are performing as expected before distributing them.

The key feature that enables this approach is the ability to flag sensitive information.

By allowing enterprise admins to tag sensitive information, Numbers Station can propagate the sensitivity to relevant assets, and track that sensitivity when copying and updating datasets. This way, enterprise admins are able to iterate with confidence on their base datasets in their base account, even with sensitive information, knowing that when these changes are distributed to customer accounts, all sensitive information will be presented for review and editing before becoming visible to the customer account.

Tagging Sensitive Information

Tagging sensitive columns ensures proper handling of data like "Employee Name" or "Org Name" that may be used in different SQL expressions before deployment.

1. Go to the Catalog of the dataset where you want to identify sensitive information.
2. Tag dimensions and metrics as sensitive using the interface (e.g., using the checkbox in the tags column).
3. Once dimensions and metrics are tagged, we propagate it to other derived dimensions, metrics, and admin feedback chats.
4. Please unmark any incorrectly tagged sensitive dimensions, metrics and saved admin feedback. You can review this by filtering for the "Sensitive" tag on the catalog and "Admin Feedback Page".
5. You can also mark any additional saved admin feedback using the toggle.