Databricks simplifies MANAGE privilege requirements for catalogs and schemas
Databricks has updated its privilege model, removing the requirement for the MANAGE privilege to also hold USE CATALOG or USE SCHEMA on the same object for catalogs and schemas. This change aims to make MANAGE behave more consistently with object ownership, simplifying permission management. While usage privileges are still needed for parent containers, this update may activate previously dormant MANAGE grants. Databricks advises auditing existing MANAGE grants to ensure they align with intended access policies.
Enhancements (1) ›
- MANAGE privilege no longer requires same-object usage for catalogs and schemas
The MANAGE privilege on a catalog or schema no longer necessitates holding USE CATALOG or USE SCHEMA on that specific object. While MANAGE on a schema still requires USE CATALOG on the parent, this change streamlines the privilege model. Databricks recommends auditing existing MANAGE grants, as previously dormant grants may now be active.
https://docs.databricks.com/aws/en/release-notes/product/2026/august#manage-no-longer-requires-use-catalog-or-use-schema-on-the-same-object
Related releases
- xAI Grok 4.6 Model Now Available on Databricks Model Serving Databricks Release Notes ·
- Databricks enhances Genie Agents with chat sharing, visualization downloads, and bug fixes Databricks Release Notes ·
- Python UDTFs in Unity Catalog Now Generally Available Databricks Release Notes ·
- Databricks Enhances Dashboards and Genie Code with AI-Powered Features Databricks Release Notes ·
- Genie One Enhancements for Task Management, Conversations, and Mobile App Login Databricks Release Notes ·
- Databricks Genie Code Now Available for HIPAA-Compliant Workspaces Databricks Release Notes ·