Unity Catalog gives Databricks a proper permission model - but managing it by hand, click by click, doesn't scale. As the number of catalogs, schemas, and principals grows, so does the risk of drift, inconsistency, and permissions nobody can fully explain anymore.

This session starts with the fundamentals: how Unity Catalog's permission model works at the catalog and schema level, how privileges are inherited, and the principles worth designing around before you write a single line of automation. From there, we go practical: a demo of a custom, YAML-driven script that treats permissions as configuration - describing who should have access to what, then applying it as a set of GRANT and REVOKE statements against the target environment.

You'll see how a declarative, config-as-code approach turns permission management into something repeatable, auditable, and safe to run again and again - closing the gap between what your permissions should be and what they actually are.