Keep Agents Running When Someone Leaves

When someone leaves your organization, their agents aren’t deleted, but automations tied to their account can stop running. Triggers run using the account and connected credentials of the person who created them. Before removing someone from Gumloop, hand off their agents, ownership, and triggers to another user. Following these four steps will help keep everything running without interruption.

​

1. Move their agents to a team

Start by moving any agents that need to remain in use out of the person’s personal space and into a team. Agents in a team remain accessible to other team members, while agents in a personal space are only accessible to their creator.

1. From the Home page, open the agent’s ⋮ menu and select Move to Team. You can also move it from within the agent.
2. Choose the destination team. If you don’t have one yet, see Create a team.
3. If the agent has attached skills, Gumloop will ask whether you want to copy or move them. Choose Move so they remain with the agent and aren’t left behind in the creator’s personal space.

The agent’s triggers and tasks move with it and will continue running as long as their creator still has access.

​

Or share the agent directly

For a simple one-person handoff, open the agent’s Access tab and add the person directly. The agent will appear in their Shared with me tab. For agents that are important to ongoing business processes, moving them into a team is usually the better long-term setup.

​

2. Add another Owner

Moving an agent into a team gives team members User access by default. Make sure at least one other user has Owner access. Owners can edit the agent, manage access, and view and manage team triggers.

1. Open the agent and go to Access.
2. Click Add owner, enter their email, and save.
3. If they’re already listed as a User, open their role and select Promote to Owner.

See Sharing roles for more details.

​

3. Recreate triggers under the new Owner

Triggers can’t be transferred between people. They continue to belong to the person who created them and run using that person’s connectors. Before the original creator leaves, have the new Owner recreate any triggers that need to keep running:

1. Open the agent’s Triggers tab. Owners can see team triggers along with their schedules and prompts.
2. Recreate each required trigger from the same tab, or just ask the agent in chat to set it up, for example: “Set up a daily 8 AM trigger that sends me this digest.”
3. Once the departing person is removed, their original triggers will automatically stop running.

If the agent should always use a shared account rather than the trigger creator’s personal credentials, you can also configure agent-owned credentials or a team connector.

​

4. Verify the handoff, then remove the member

Before removing the departing person, confirm that the replacement triggers are running successfully and that the new Owner can access everything they need. Check the Triggers tab and recent tasks for any failed runs. Once everything looks good, remove the departing member from Organization → Members. Removing them from Gumloop is what disables the triggers still tied to their account.

​

Make sure everything has been handed off

Before the person leaves, it can help to review everything they’ve created. You can ask the analytics agent in Gumball or Insights something like: “List the agents, triggers, and skills I created.” Use that list to identify anything that still lives in a personal space or depends on the departing person’s account.

​

If the person has already left

An organization admin can still recover most team-owned work.

1. Find what they created. Use the analytics agent to identify their agents, triggers, and skills, or export agent data with Creator Email through Usage Data Export.
2. Claim ownership. Open the agent using admin access, click the ⋮ menu beside its name, and select Claim Ownership. See Claim an ownerless agent.
3. Recreate the triggers. Claiming ownership gives you control of the agent, but it doesn’t restore the previous owner’s triggers. Recreate them under another user.

​

Related