Going further

Flow ownership

Every flow has an owner — whoever created it, to start. It matters for one concrete reason: drift alerts go to the owner. When the database changes under a flow, the owner is who gets told, so the owner should always be someone who’s still here.

1. Open the flow’s inspector to see its owner.

   This isn’t just a label — it’s who drift notifications reach for this flow.

2. Reassign it from there. Anyone who can edit the flow can hand it to any current team member.

   Ownership is editable on purpose, so you can pass a flow on when responsibility moves — no admin needed.

3. When an owner leaves the organization they show as (former member), and drift on that flow then has no one to notify — the inspector flags it. Reassign it to a current member to start alerts reaching someone again.

   This is the quiet failure: a departed owner means drift is still detected but never announced. Reassigning is the fix.