1. Latest Release Home
  2. Guides
  3. Concepts
  4. Tools
  5. References
  6. Integrations
  7. Data applications
  8. Release Notes
  9. Incorta Premium
  10. Release Support Policy
  11. Release Model

Data Catalog Manager → Configure Classification Levels

The Data Catalog Manager enables Data Governors to configure classification levels in the Data Catalog, manage data masking behavior, and control access to unmasked data.

Note

Only users with the Data Governor role can configure and modify classification levels and apply classifications to data.

Access the Classification Configuration

  1. Navigate to the Data Catalog tab in the top navigation bar.
  2. Select the Configure Classification button in the top-right corner of the page.
  3. The Classification configuration dialog will appear.

Edit Classification Levels

  1. In the Classification configuration dialog, hover over the classification level you want to modify.
  2. Select the edit (pencil) icon that appears.
  3. In the Edit Classification dialog, you can:
    • Modify the Name of the classification level.
    • Update the Description to clarify the classification purpose.
    • Toggle Mask Data option to enable/disable data masking for this level.
    • Assign groups that will have permission to view unmasked data.
  4. Select Save to apply your changes.
Note

Data masking is currently not applied in SQLi. Refer to Known Limitations for more information.

Apply Classifications to Data

Data classification in Incorta is applied through Business Terms in the Glossary. This approach allows for consistent classification across multiple data assets. Refer to Create a Business Term with Classification for more information.

View Applied Classifications

Once classifications are applied through business terms, they become visible in the Data Catalog when viewing tables and columns. Users will see the classification level associated with specific data elements, and data masking will be applied based on classification settings.

Known Limitations

Masked columns are not supported in the following scenarios and will display data in plain text, without masking applied:

  • When using the WITH statement in Advanced SQLi queries (Resolved in 2024.7.5)
  • When using LATERAL subqueries in Advanced SQLi queries (Resolved in 2025.7)
  • When querying non-optimized tables via Advanced SQLi (Resolved in 2024.7.5)
  • In insights generated based on Spark SQL result sets that reference the masked columns (Resolved in 2025.7)
  • In insights generated based on Analyzer result sets that reference the masked columns (Resolved in 2024.7.5)
  • When accessing data via the classic SQL Interface
  • When querying data using PostgreSQL views
  • When using the getColumn function.