One of the biggest challenges in security-conscious enterprises is getting timely access to the right data. Data owners often juggle a flood of requests, while data consumers wait days—or even weeks—for approvals, slowing down analysis and decision-making. With Unity Catalog’s new Request for Access feature, you can eliminate bottlenecks by enabling self-service access requests directly from within Databricks, so the right people get the right data, faster, without sacrificing governance.
In this blog, we’ll explore how admin teams can get started by setting up access request destinations, explain how users can make access requests, and provide guidance on having a distributed model for access approvals with central admin oversight.
Request for Access streamlines data access provisioning for multiple personas:
Before users can request access, admins must configure access request destinations. These can be set at the catalog or schema level, and the configuration is inherited by all objects within them (tables, views, models, etc.).
You can choose from three destination types:
💡Tip: Admins can set catalog owners as the default email destination for all catalogs via a toggle in the workspace admin page.
Once destinations are set, your users can request permissions from several in-product surfaces:
Users can request access for themselves or on behalf of another user, group, or service principal. Requests are automatically sent to the destination set up by the admin.
User requesting access from catalog explorer:
User requesting access from a dashboard panel:
When a request is made, the configured destination receives all relevant details including the requester’s name, object name, permissions requested, who the request is on behalf of (if different than requester), and reason for the request.
Approvers can click Open Permission Settings to go directly to the approval screen, where they have two options:
Using the group approach allows users that do not have ownership / MANAGE privilege on an object in Unity Catalog to approve access requests for it. It can also be used by admins to keep control over what permissions can be provisioned to users (e.g. a group with only SELECT ensures only read access is granted).
By enabling Request for Access in Unity Catalog, you can democratize data discovery, streamline data access approvals, and empower teams to work with data faster, while maintaining governance.
To get started: