Unity Catalog: the governance layer

Unity Catalog: the governance layerone place to grant, trace and audit

Tables alone don't make a platform governable. Unity Catalog sits above the workspaces and gives every table a three-level name - catalog.schema.table - with access control, lineage and audit attached to that name rather than to a cluster.

• Centralized RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually. Press Enter for the full definition.. Grant on catalogs, schemas or tables once; it holds across every workspace and compute type instead of being re-pasted per cluster.
• Column and row controls. Column masks and row filters let you expose a table while hiding PIIPersonally Identifiable Information. Data that can identify a person (names, emails, SSNs); regulated and sensitive. Press Enter for the full definition. columns or restricting rows by group - the lever you reach for with sensitive product data.
• Lineage and audit. Unity Catalog tracks table- and column-level lineage and logs access, which is how you answer "where did this number come from" and "who read this PIIPersonally Identifiable Information. Data that can identify a person (names, emails, SSNs); regulated and sensitive. Press Enter for the full definition." without a forensic dig.