Databricks Unity Catalog - Table ACL The main feature of Unity Catalog is to provide Unity Catalog you an easy way to setup Table ACL (Access = Control Level, but aso build Dynamic Views Management Catalogs Acness Controls based on each individual permission. ‘Audit logs ‘Typically, Analysts will nly have access to customers from their country and won't be able to read GOPR/Sensitive informations (like emai, Databricks mene firstname etc) Workspace Workspace ‘Atypical workflow in the Lakehouse architecture Clusters Clusters i the tokowing SQL Endpoints SQL Endpoints + Data Engineers /Jobs can read and update the main data/schemas (ETL part) + Data Scientists can read the final tables and update their features tables ‘+ Data Analyst have READ access to the Data Engineering and Feature Tables and can ingest/transform additional data in a separate schema ‘Data is masked/anonymized dynamically based on each user access level With Unity Catalog, your tables, users and groups are defined at the account level, cross workspaces. Ideal to deploy and operate a Lakehouse Platform across all your teams. Let’s see how this can be done with the Unity Catalog