This is the moment you realize your Databricks workspace needs restricted access and tight access control, not tomorrow, now.
Databricks is a powerful platform, but without the right permissions and policies, it can be a free-for-all. Restricted Access in Databricks Access Control is about setting clear boundaries, enforcing least privilege, and making sure every user and service has only the exact rights they need—no more, no less.
The foundation is workspace-level access control. Define which users can even log in. From there, move into cluster-level permissions, ensuring compute resources are available only to trusted users, and block sensitive clusters from public use. For notebooks and jobs, lock them down to specific groups or roles. Always tie permissions to groups, not individuals, so changes scale cleanly as your team changes.
Table Access Control (TAC) is your guardrail for data. Use it with Unity Catalog or Hive metastore to set granular permissions at the schema, table, and column levels. Combine TAC with row-level security to keep sensitive records away from unauthorized users without duplicating datasets.