What actually belongs to the person leaving
In Make, scenarios, connections and other items belong to a team, not to the individual who built them. Make says items always belong to only one team and you cannot change which team an item belongs to. [2] So removing a person does not by itself delete their scenarios.
What does stay personal is harder to see. A connection that a freelancer authorized with their own Google login uses their Google grant. A MailerLite token they generated is permanently bound to them [9], and MailerLite says even an account admin cannot see tokens created by other users. [10] Make API tokens live in each person's profile under API access. [7] And Make's error, warning and deactivation emails are configured in each person's own profile [12], so the alerts may leave with them.
The handover goes best while the person is still around for one last session. The steps below assume they are; where they are not, the same steps work, with more reconnecting.
Step 1: inventory before anyone is removed
Ask the departing builder to open Make's Connections page and use the My connections filter, which shows only connections they created. [3] Export that list into your runbook along with which external login each one uses. All users in a Make team can use and manage connections created in that team [3], so the inventory, not access, is the hard part.
Next, export a blueprint of every active scenario. Make's blueprint is a .json file with the scenario's modules, module settings and mapped values; connections are not included. [5] It is your rollback copy if a replacement connection breaks something.
| Item | Where to find it | Tied to the person? | Handover action |
|---|---|---|---|
| Organization ownership | Organization settings [1] | Yes, if they are the Owner | Transfer ownership before removal [1] |
| Team membership and role | Team members list [2] | Yes | Set role to None after handover [2] |
| Scenarios | Team scenarios [2] | No, owned by the team [2] | Export blueprints; assign a new owner in the runbook [5] |
| Connections they created | Connections, My connections filter [3] | Often, via their app logins | Create replacements under company logins and swap them in [4] |
| Webhooks | Webhooks list [6] | No, but they may depend on their connections | Confirm each still has a scenario and recent log entries [6] |
| Make API tokens | Their profile, API access tab [7] | Yes | Create new tokens under a company user and update scripts [7] |
| Third-party API keys | Each source app | Yes for MailerLite tokens [9] | Create new keys and delete or reset the old ones [8][11] |
| Error and deactivation emails | Their profile email preferences [12] | Yes | New owner turns them on in their own profile [12] |
Step 2: transfer the organization and set roles
If the departing person is the organization Owner, only they can hand that over. Make's Owner role is the only one that can transfer ownership or delete the organization. [1] The path is Org in the left sidebar, then the user menu, Organization settings, Transfer ownership, choose the new owner, and Save. The new owner must already have accepted their invitation. [1] Get this done before their last day; nobody else can do it for them.
Then check team roles. Team Admin manages members and settings, Team Member has full access to team resources, Team Operator can activate, deactivate and schedule scenarios, and Team Monitoring is read-only. [2] Make sure at least two remaining people hold a role that can pause a scenario. On plans below Teams, an organization has a single team and roles cannot be managed within it. [2]
Step 3: replace connections tied to their logins
For each connection on the inventory that uses the person's own login, create a new connection with a company-owned account, then point modules at it. Make documents two ways to do the swap. Within one scenario, the Make DevTool browser extension has a Swap Connection tool that updates all modules of the same app when you leave the target module empty. [4] Across many scenarios, you build a scenario with the Make app that lists connections, searches scenarios, fetches each blueprint, replaces the old connection ID and updates the scenario. The Make app is only available on paid plans, and Make advises testing on one or two scenarios before applying it in bulk. [4]
After the swap, run each scenario once and check the output. Make warns that a module using a connection with insufficient scopes ends the scenario with an error. [3]
Delete the old connection last. If a webhook uses a connection, Make requires you to delete the webhook before the connection. [3]
Step 4: rotate keys at the source apps
Removing someone from Make does not invalidate the keys they generated elsewhere. Rotate at the source.
MailerLite: create a new token from a company-owned user, update the Make connection, then have the departing person remove theirs, because only the creator can see their tokens. [9][10] Kit: in the Developer tab of account settings, edit the key and choose Reset to issue a new value or Delete API Key to remove it; after a reset, anything using the old key stops authenticating. [8] Google: the person can remove a third-party app's access from myaccount.google.com/linkedapps, which stops that app reaching their account. [11] Make API tokens: create new ones under a company user from Profile, API access; the full token is only shown once. [7]
Leaving the person's Google grants in place is not a stable plan either. Google lists reasons a refresh token stops working, including the user revoking access, the token going unused for six months, and a password change when the token includes Gmail scopes. [13] Any of these can happen to a departed person's account without warning, so replace the connection rather than wait for it to fail.
Step 5: moving scenarios to another team or organization
Because items cannot change teams [2], moving a scenario means rebuilding it from its blueprint. Create a new empty scenario in the destination, choose Import blueprint from the three-dot menu, pick the .json file and Save. [5] Then create connections in the destination, make any edits, set the schedule and save. [5] Blueprints must be under 2 MB. [5]
Treat webhooks as new. Make's blueprint page promises modules, settings and mapped values only [5], so plan to create a fresh webhook in the destination and paste its URL into each sending app. Once the old scenario is switched off and its webhook is no longer connected to any scenario, Make deactivates that webhook after 5 days. [6]
Step 6: confirm webhooks still fire
For each webhook scenario, trigger a real test event from the sending app and check the webhook log and the scenario's History tab. Make keeps webhook logs for 3 days, or 30 on Enterprise [6], so do this within days of the handover, not at month end. The History tab lists runs with status and operations, and records edits and activations in the change log. [14]
- Organization ownership transferred by the departing Owner. [1]
- At least two people can pause scenarios after the departure. [2]
- Blueprint exported for every active scenario. [5]
- Every connection from the My connections inventory replaced with a company-owned login. [3][4]
- Old webhooks deleted before old connections. [3]
- MailerLite, Kit and other API keys rotated at the source. [8][9]
- Google access removed from the departing person's linked apps. [11]
- Error and deactivation emails switched on for the new owner. [12]
- A live test event seen in each webhook log within 3 days. [6]
- Departing person's team role set to None, then removed from the organization. [1][2]
Questions before you decide
Do Make scenarios get deleted when the builder is removed?
Make says items belong to a team, not a person, and cannot change teams. Removing someone does not move their scenarios, but connections made with their personal logins can stop working.
Who can transfer ownership of a Make organization?
Only the current Owner. They go to Organization settings, Transfer ownership, pick the new owner and save. The new owner must already have accepted their invitation.
How do I move a Make scenario to another team?
Export its blueprint as a .json file, create a new scenario in the destination team, import the blueprint and save. Then create connections, set the schedule and create a fresh webhook if it uses one.
Can I swap a connection in many Make scenarios at once?
Yes. Make documents a scenario built with the Make app that finds scenarios using the old connection ID and updates their blueprints. The Make app needs a paid plan, and Make advises testing on one or two scenarios first.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make Help: Organizations Accessed 30 Oct 2026
- Make Help: Teams Accessed 30 Oct 2026
- Make Help: Connect an application Accessed 30 Oct 2026
- Make Help: Replace connections across multiple modules Accessed 30 Oct 2026
- Make Help: Blueprints Accessed 30 Oct 2026
- Make Help: Webhooks Accessed 30 Oct 2026
- Make Help: API key Accessed 30 Oct 2026
- Kit developer docs: API authentication Accessed 30 Oct 2026
- MailerLite developer documentation: authentication Accessed 30 Oct 2026
- MailerLite Help: Where to find the MailerLite API key, group ID and documentation Accessed 30 Oct 2026
- Google Account Help: Manage connections between your Google Account and third-party apps Accessed 30 Oct 2026
- Make Help: Manage your email preferences Accessed 30 Oct 2026
- Google for Developers: Using OAuth 2.0 to access Google APIs Accessed 30 Oct 2026
- Make Help: Scenario history Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.