https://community.databricks.com/t5/data-engineering/high-level-strategy/m-p/151422#M53644 <P>To handle fine-grained access control across multiple Databricks workspaces, most teams rely on Unity Catalog, which provides centralized governance with workspace-level restrictions, object-level privileges, and attribute-based policies (ABAC). For better discoverability, catalogs are often structured by domain (e.g., Sales, Marketing, Finance) or environment (Dev, Test, Prod), with consistent naming conventions.</P><P>Databricks Unity Catalog offers several complementary models for access control:</P><UL><LI><STRONG>Workspace-level restrictions:</STRONG> Limit which workspaces can access specific data objects.</LI><LI><STRONG>Privileges &amp; ownership:</STRONG> Grant permissions on securable objects (catalogs, schemas, tables, views).</LI><LI><STRONG>Attribute-based access control (ABAC):</STRONG> Use governed tags and policies to restrict access dynamically.</LI><LI><STRONG>Table-level filtering &amp; masking:</STRONG> Apply row filters or column masking to control visibility of sensitive data.</LI></UL> Thu, 19 Mar 2026 14:20:37 GMT Bhaskar_Patil87 2026-03-19T14:20:37Z https://community.databricks.com/t5/data-engineering/high-level-strategy/m-p/151347#M53631 <P>Hello,&nbsp;</P><P>How are you handling fine-grained access control across multiple workspaces? I’d love to hear how others are structuring their catalogs for better discoverability.&nbsp;</P> Thu, 19 Mar 2026 05:58:21 GMT https://community.databricks.com/t5/data-engineering/high-level-strategy/m-p/151347#M53631 herry067broof 2026-03-19T05:58:21Z