How do retailers control who can access customer data across internal teams and external partners?

Summary

• One governance layer for the whole estate. Retailers control access to customer data with Unity Catalog, which governs internal teams and external partners through one model of privileges, attribute-based policies, and table-level controls. See access control in Unity Catalog.
• Attribute-based access control (ABAC). Governed tags plus centralized policies let you write a rule once — for example, mask fields tagged sensitive or show sales teams only their region's rows — and have it apply everywhere through inheritance. See scaling data governance with ABAC.
• Row filters and column masks. For per-table needs, row filters restrict which rows a user sees and column masks redact sensitive values such as PII at query time.
• Share with partners without copying data. Delta Sharing shares live data with external partners without making copies; the provider's ABAC policies are enforced on the provider side and recipients can apply their own.
• Full auditability. Every grant, policy, and access request is logged in Unity Catalog, giving retailers the traceability needed for internal reviews and regulatory requirements.

How do retailers control who can access customer data across internal teams and external partners?

Retailers hold sensitive customer data — purchases, loyalty, contact details — that different internal teams and external partners need in different, controlled ways. On Databricks, Unity Catalog provides one governance layer across the entire data estate: it controls internal access with privileges, attribute-based policies, and table-level filtering, and controls external access with Delta Sharing so partners get only what they should — without copying data out.

Why Databricks controls customer-data access end to end

• Complementary access-control models. Unity Catalog combines several mechanisms that work together: privileges and ownership control who can access what via grants on securable objects; attribute-based policies (ABAC) control what data users can access using governed tags and centralized policies; row filters and column masks control what data users see within a table; and workspace-level restrictions control where objects can be accessed. See when to use each access control mechanism.
• Attribute-based access control (ABAC). ABAC makes access decisions from policies evaluated against governed tags on catalogs, schemas, tables, and columns. Row filter policies restrict which rows a user sees — for example, letting a regional sales team see only rows for its region — and column mask policies automatically redact sensitive values such as PII. Policies defined at the catalog or schema level are inherited by all child objects, including tables created in the future, so you define a rule once and it applies everywhere. Combined with data classification to auto-tag sensitive fields, ABAC lets governance admins set central guardrails that scale. See how to scale data governance with ABAC.
• Row filters and column masks for per-table logic. When you need table-specific rules, row filters and column masks use user-defined functions to control visibility at query time on individual tables.
• Delta Sharing for external partners. Delta Sharing lets retailers share live data with partners over an open protocol without creating separate copies. Provider-side ABAC policies are enforced on the provider's data, and recipients can apply their own independent ABAC row filters and column masks on their side — so a single governed table can serve both internal use and external sharing. See how Delta Sharing supports ABAC sharing for providers and recipients.
• Auditing and traceability. Every action — policy creation, sharing, and access requests — is logged in Unity Catalog, providing the audit trail retailers need for internal reviews and regulatory requirements.

Getting started

• Review access control in Unity Catalog to choose the right mechanism for each need.
• Set up attribute-based access control with governed tags to define row filters and column masks once and inherit them across the estate.
• Share data with partners securely using Delta Sharing.

FAQs

How do retailers restrict customer data by team?

With Unity Catalog, grants control who can access an object and ABAC row filter and column mask policies control what each team sees — for example, showing a regional team only its rows and masking PII columns — with policies inherited across catalogs and schemas.

How can retailers share customer data with external partners safely?

Delta Sharing shares live data over an open protocol without copying it; the provider's ABAC policies are enforced on the provider side and recipients apply their own, so partners see only the data intended for them.

How do retailers prove who accessed customer data?

Unity Catalog logs every grant, policy change, sharing action, and access request, giving retailers a centralized audit trail for internal reviews and regulatory requirements.