Skip to main content Skip to complementary content

Finding and hiding sensitive data with a sensitivity label

Assign the highly confidential sensitivity label to the email_address column in the anonymized_orders table. If you have already found and hidden the sensitive data automatically with a data classification, no need to follow those steps.

Before you begin

  • You have been assigned an object role with the Data Management capability.

  • You have been assigned an object role with the Data Classification Editing capability.

About this task

The highly confidential label identifies highly confidential data, it includes customer private data (PII protected under GDPR).
When applying this sensitivity label, you identify a data asset as sensitive and its data is hidden automatically from unauthorized users.


  1. In the search box, type in email columns.
    The email_address columns from the ACME customer hub database display in the search results.
  2. On the toolbar, click Columns and select the Grid view.
  3. Drag and drop the Sensitivity Label column from Available columns to Selected columns to display it.
    Sensitivity labels may already have been automatically assigned to some columns.
  4. Select all the email_address columns.
  5. Right-click and select Edit.
  6. Select Sensitivity Label, Replace in the Action column, and Highly Confidential in the Value column.
  7. Click Ok.
  8. Open the object page of the email_address column. The Highly Confidential sensitivity label is displayed in the header.
  9. Go to the object page of the anonymized_orders table.
  10. Click the Data Sample tab.
    The email_address column data is grayed out.
    When previewing sample data from the anonymized_orders table without the Object role with the Data Management Capability, data values of PII are replaced with a string of # number signs.


You are ready to tag the table to indicate that it is compliant with the data protection rules. For the next step, see Labelling a data asset.

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!