Showing and Hiding Sample Data and Profiling Results
Sampled data and the profiling results are hidden from most users by default. One must be assigned the Data Viewing or Data Owner capability object role assignment for the model in question.
One may even mask or hide this information even from a Data Viewer . To do so, one must either:
- Have the Data Classification Editing capability object role assignment for that metadata and assign a sensitivity label which has data hiding .
- Classify imported objects where a data class has a sensitivity label assigned to it which has data hiding .
- Specify that all imported objects in a model are automatically hidden by default by way of a sensitivity label.
There are however, inferred sensitivity labels so that when you apply a sensitivity label to an imported object, e.g. a column, then all the imported objects “downstream” in the data flow lineage will be given at least that level of sensitivity as "Sensitivity Label Lineage Proposed". This means you will see automatic sensitive label tagging by inference across the enterprise architecture. As with "Sensitivity Label Data Proposed", the "Sensitivity Label Lineage Proposed" can be rejected, therefore stopping the propagation of inferred sensitivity labels in that data flow direction. Note that the propagation of inferred sensitivity level is also not inferred by any data masking discovered within the ETL/DI/Scrip imports involved in that data flow.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!