in this guide
  1. a connection is a saved sign-in
  2. what each platform does when the builder leaves
  3. two endings, neither chosen
  4. the controls an admin actually has
  5. give the flow an owner who does not leave

Picture a 150-person distribution company. Three years ago a finance coordinator got tired of copying invoices by hand, so she built a flow one afternoon: when a supplier invoice lands in the invoices inbox, save the PDF to a finance folder, create a draft bill in the accounting tool, and post a note in the finance channel. It has run every working day since. Nobody else has opened it.

Every step of that flow signs in to another system. The inbox step uses a connection she authorised with her own account. So do the folder step, the accounting step and the chat step. The automation platform stores those sign-ins and replays them on a schedule, as her, for as long as they stay valid.

how a flow ends up holding one person's access

  1. 1built in an afternoonOne person wires four systems together.
  2. 2each step signs in as herThe platform saves her connection to every app.
  3. 3she leavesThe leaver checklist closes her accounts. The flow is on nobody's list.
  4. 4two possible endingsThe flow keeps her access, or the invoices stop a few weeks later.

The risk in general is covered on the automation sprawl page. This guide is about the part underneath: whose credentials the flow uses, what Zapier, Make and Power Automate actually do when that person leaves, and which controls an admin has. It pairs with the identity you can’t offboard, because a flow like this is a service account that nobody created on purpose.

a connection is a saved sign-in

Microsoft’s data policy documentation for Power Platform says plainly that connections “represent a saved credential”. The same holds on the other platforms. When someone adds a mailbox step, the platform asks them to sign in to the mailbox, and from then on the flow can do in that mailbox whatever the person could do there.

That has three consequences worth knowing.

The flow’s reach is the builder’s reach. A flow that only needs to read one folder of invoices holds a connection to the whole mailbox, because the connection is to the account. If the builder is an admin in the accounting tool, the flow’s connection is an admin connection.

Other people can use it. Zapier’s help centre says that sharing a connection to an email account lets the people it is shared with read emails in that account, and that shared users can use the connection in their own Zaps. In Power Automate, Microsoft’s sharing documentation says co-owners can use the services in a flow but cannot change the credentials of a connection another owner created. Either way, the sign-in belongs to one person and the use spreads to several.

The identity provider sees a consent, and little after it. Microsoft’s Entra documentation says that by default all users can consent to apps for permissions that do not need an admin, for example access to their own mailbox. Google’s admin console lists third-party apps that accessed Workspace data with a count of users per app. Both show that a platform holds access. Neither shows which flows use it or what they do.

A flow can do whatever its builder could do, for as long as the saved sign-in lasts.

what each platform does when the builder leaves

This is where the vendors differ, and where the surprises are. All of the following comes from each vendor’s own documentation as read in November 2026.

Zapier. When a member is removed from a Team or Enterprise account, Zapier’s help page says ownership of their Zaps and app connections transfers to the person chosen during removal. If an admin does the removal, everything goes to the account owner instead, and the same happens when the user is deprovisioned through SCIM. For private connections, the remover picks one of two options: the connections expire 30 days after removal, or they keep working until they expire on the connected app’s own schedule. Shared connections keep working, in Zapier’s words, “as long as the user’s app account exists”. So the Zap gets a new owner in Zapier, while the connection inside it still depends on the leaver’s account in the mailbox or CRM existing. Zapier also offers a CSV of the member’s Zaps and connections, which can be downloaded from the members page only while the person is still a member; the emailed link is valid for 7 days.

Power Automate. Microsoft’s sharing documentation says a shared flow keeps running if it still has an active owner, and that actions using connections belonging to the person who left might fail. A flow with no valid owner is what Microsoft calls an orphaned flow, and its troubleshooting article says such flows can fail if they use connections tied to that user. Admins can find them in the Power Platform admin center, where they show no owner, or through PowerShell with Get-AdminFlow -CreatedBy. One detail matters for planning: for flows outside a solution, Microsoft says the owner cannot be changed in place “because the owner is part of the flow identity”. It has to be recreated by the new owner through a copy, Save as, or export and import.

Make. Make’s help centre says scenarios, connections, webhooks and data stores belong to a team, and that each item always belongs to only one team. Its pages on teams and organisations describe how to remove a user and say nothing about what happens to the connections that user authorised. If you run Make, treat that as an open question to test in your own account before someone leaves.

Microsoft adds two timers that can end a flow without anyone deciding to. Its limits page says a flow whose trigger or actions fail continuously is turned off after 14 days, and a flow that is not triggered within 90 days might be turned off unless its owner has a premium or capacity licence, with a notice to owners 30 days before.

what the leaver checklist closes, and what the flow still holds

what offboarding closes

the usual checklist

  • Sign-in to the identity provider
  • The laptop and the badge
  • Membership of the automation platform

what the flow still holds

until a token expires or an account is deleted

  • Saved connections signed in as the leaver
  • Shared connections other people's flows depend on
  • Webhooks and schedules that keep firing

two endings, neither chosen

The vendor behaviour above produces one of two outcomes, and which one you get depends on details nobody looked at.

The flow keeps running as the leaver. If the person’s mailbox or CRM account is kept alive, for example for retention or because a colleague is covering, the connection may stay valid, and the flow goes on reading and writing as someone who no longer works there. The token guide explains why disabling the sign-in does not, by itself, end grants already handed to other apps.

The flow stops. If the account is closed properly, the connection dies, and the flow fails on its next run. In the scenario above, that is the invoices. In that scenario nobody links the failure to the leaver, because nobody knew the flow existed.

The platform holding the sign-ins is also a place where they can be stolen together. Google Threat Intelligence Group reported that between at least 8 and 18 August 2025, an actor it tracks as UNC6395 used compromised OAuth tokens of the Salesloft Drift integration to reach customers’ Salesforce instances, and used tokens of the Drift Email integration on 9 August to access email from a very small number of Google Workspace accounts. Salesloft and Salesforce revoked the Drift application’s tokens on 20 August. That case is told on the Drift incident page. An automation platform holds the same kind of tokens, for every flow your team has built.

the controls an admin actually has

The useful controls exist, but several sit on top-tier plans, and none of them retrofits an owner onto a flow that has none.

  • Zapier app access policies. Zapier’s help centre lists allow lists and restrict lists of apps as Enterprise-only. If an app is blocked, the Zap stays on and steps using that app are held when it runs.
  • Zapier managed apps. Also Enterprise-only: for a chosen app, only admins can create, share and delete connections. Zapier says existing connections members created are not removed, so the cleanup is still yours.
  • Power Platform data policies. Admins sort connectors into groups and block some. Microsoft says flows that break a policy are suspended and connections to a blocked connector are disabled, with enforcement taking up to 24 hours in the most extreme cases and usually under an hour.
  • Consent settings in your identity provider. Microsoft recommends allowing user consent only for apps from verified publishers, and notes that changing the setting affects future consents only; existing grants stay until revoked. Google’s API controls let an admin mark each app Trusted, Limited, limited to specific data, or Blocked.

give the flow an owner who does not leave

The durable fix is to move the sign-in off a person.

In Power Automate, a solution-aware flow can be owned by a service principal application user. Microsoft’s ownership page says that in this case ownership “isn’t tied to a user that could leave the organization”, and that the flow’s connections must be shared with that application user. Flows outside a solution have to be moved into one first, where your environment allows it.

In Zapier, connect the shared account. Zapier’s own help suggests creating a separate account in the app to share, for example a shared mailbox in place of a personal one. That account then needs an owner and a password policy of its own; the invoices inbox guide covers who can read one.

Every flow that matters gets two names. One person who owns what it does, and one who can open it if the first is away. A long absence tests this as surely as a departure, which is why the leave guide sends readers here.

The leaver step runs before the account closes. Export the person’s flows and connections while the export still works, decide per flow whether to re-own, rebuild on a shared identity or retire it, and only then revoke the grants. The hour you have not planned puts the automations after the first hour; for an ordinary departure they belong in the week before.

Bots and apps installed in chat tools follow the same pattern with their own token types, covered in the Slack apps guide.

Which flows in your company would stop the day their builder’s mailbox is closed, and which would keep running as someone who is gone?

read next in the appsB16 the bot that can join every channelany member can add an app to the company chat in a minute. the app gets a token that can join public channels and read them, and it keeps working after the person who added it leaves. who added yours?

sources

  1. Zapier Help Center: Remove members from your Team or Enterprise account
  2. Zapier Help Center: Share app connections with members of your Team or Enterprise account
  3. Zapier Help Center: App access policies in Zapier
  4. Zapier Help Center: Manage app connections with managed apps
  5. Microsoft Learn: Manage orphaned flows when owner leaves organization
  6. Microsoft Learn: Share a cloud flow
  7. Microsoft Learn: Change the owner of a cloud flow in Power Automate
  8. Microsoft Learn: Limits of automated, scheduled, and instant flows
  9. Microsoft Learn: Data policies (Power Platform)
  10. Microsoft Learn: Configure how users consent to applications (Microsoft Entra ID)
  11. Google Workspace Admin Help: Control which apps access Google Workspace data
  12. Make Help Center: Teams
  13. Google Threat Intelligence Group: Widespread data theft targets Salesforce instances via Salesloft Drift (August 2025)