The fastest path to running models asks for broader access than the account was designed to allow.
The customer needs usable production jobs while its security boundary protects warehouse schemas.
Who you’d be doing this for
“I’ve had to rerun the same models from my own session twice today, and Finance is asking where the refresh went.”
Leire Marino · Analytics Engineer
Owns the curated models whose scheduled dbt Cloud runs are blocked by the warehouse-role mismatch.
What is at stake
All 18 scheduled dbt Cloud jobs failed after SCIM provisioning changed warehouse-role access. You must weigh first-day activation against the customer’s least-privilege boundary.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- first-day activation vs least-privilege access
- narrow role mapping vs broad warehouse grants
- rapid correction vs reusable setup pattern
Why Fivetran
dbt Cloud Guided Setup succeeds only when identity, warehouse access, and production execution work together on the customer’s first day.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, 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.