Access workflows often trade clarity for speed until broad permissions become the easiest path.
People need enough context to request and approve the right scope without turning every decision into a prolonged review.
Who you’d be doing this for
“I need the table today, but I don’t want to ask for the keys to everything.”
Fiona Fontaine · Lead Data Engineer
Requests governed customer and operational datasets for cross-domain transformation pipelines.
What is at stake
29% of recent governed-dataset requests ended in workspace-wide or owner-level grants, with purpose and scope unclear at decision time. You have to keep access fast without locking in permissions that are expensive to unwind.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- timely access vs. least privilege
- request simplicity vs. decision evidence
- generated recommendations vs. mandatory verification
- migration durability vs. easy rollback
- security assurance vs. analytical momentum
Why Databricks
At Databricks, it often matters because shared analytics depends on access that is both timely and appropriately bounded.
Written with these in mind
Not your kind of problem? 34 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.