> ## Documentation Index > Fetch the complete documentation index at: https://docs.dataleap.ai/llms.txt > Use this file to discover all available pages before exploring further. # Hand over agents when you leave > Before you leave or change roles, decide which agents stay personal, which become templates, and which move to a team. Leaving the company, ending a contract, or moving to another role? Decide for each agent where it belongs. Then move the ones other people rely on into a team before your access ends. ![Diagram: an agent that only helps you stays personal and is turned off when you leave; an agent colleagues could use becomes a template they deploy themselves; an agent that does your team's work is moved to a team, which keeps it running](https://mintcdn.com/dataleap-469bb19d/tcdnF8cwUwsx0EQD/images/hand-over-agents-light.svg?fit=max\&auto=format\&n=tcdnF8cwUwsx0EQD\&q=85\&s=819f5e2f1b4d7fbbaeae83488907d54c) Where each kind of agent goes before you leave. ## What happens when you leave Once you're removed from your organization in Dataleap: | | What happens | | - | - | | **Your personal agents** | They're turned off, so they stop running. This includes agents you shared with others. | | **Team agents** | They stay with the team and keep running. | | **Your own accounts** | They leave every team with you. Team agents that used them lose those tools and triggers. | | **Skills you own** | They're deleted, including skills you shared with a team. | So the agent itself is rarely the problem. What breaks is anything still tied to you: your personal space, your accounts, and your skills. ## Decide where each agent belongs | The agent | Do this | | - | - | | Only helps your own productivity, such as your inbox or your notes | Nothing. It's tied to you, and nobody else needs it. | | Would help colleagues with their own work | Share it as a [template](https://docs.dataleap.ai/share/templates.md). Each colleague deploys their own copy and connects their own integrations. | | Does work for your team, or others rely on its results | Move it into a [team](https://docs.dataleap.ai/share/team-spaces.md) with **Move to team**. The team then owns it, so it keeps running after you leave. | [Sharing an agent](https://docs.dataleap.ai/share/share-an-agent.md) with **Can use** or **Can edit** doesn't hand it over. It's still your personal agent, so it's turned off when you leave. Work that belongs to a team should live in a team space anyway, not only when someone leaves. [When to share what](https://docs.dataleap.ai/share/when-to-share-what.md) has the full decision guide. ## Move a team workflow into a team **1. Pick or create the team** The agent goes into a team you're a member of. Your teams are listed under **Teams** in the sidebar, and **All teams** shows every team in your organization. If no team fits, create one: click **+** next to **Teams**, enter a name, and add your successor, for example your manager, under **Add Members**. You become the new team's admin. **2. Move the agent** Open the agent's actions menu and choose **Move to team**. Pick the team, review what the move changes, and click **Move**. The team gets the agent itself. Its chats, runs, files, memory, database, triggers, versions, apps, and weekly budget limit all come along, so you don't have to rebuild anything. See [Move an agent into a team](https://docs.dataleap.ai/share/team-spaces.md#move-an-agent-into-a-team) for everything the review lists. **3. Replace your own accounts** Your own accounts stay on the agent after the move, so it keeps running for now. But they're still yours, and they leave the team when you leave. Before you go, have your successor connect the integrations with a [Shared account](https://docs.dataleap.ai/share/team-spaces.md#accounts-in-a-team), such as a team or service login, or with their own account. Then tell the agent in its chat to use those instead of yours. **4. Make your successor a team admin** Open the team, click **Settings**, and under **Members** open the **⋯** menu next to your successor's name. Choose **Make team admin**. Team admins can manage every agent in the team and add new members. A team's only admin can't leave it. > [!NOTE] > > On Enterprise plans, an organization admin may need to approve a new team's budget before its agents can run. ### What the move changes * **What comes along:** chats, runs, files, memory, database, triggers, versions, apps, and the weekly budget limit. * **Past chats and runs** become visible to the team. They may contain data from your accounts. * **Your own accounts** stay on the agent, so it keeps working. They're still yours, which is why step 3 replaces them. * **Other people's accounts** come off the agent, and so do accounts that belong to another team. Their tools stop working, and their triggers are deleted. If anything comes off, the agent turns off until it's fixed. The setup chat gets a note with the steps. * **Apps that call other agents** come along too, but an app can only call agents in the same space. If an app calls another of your agents, move that agent as well. You can't move an agent while it's working. Stop what's running or let it finish, then check again. ## Hand over your skills Skills you own are deleted when you leave, even if a team agent uses them. Before you go, [export](https://docs.dataleap.ai/scale/skills.md#import-and-export-skills) each skill others need. A teammate imports it, shares it with the team, and asks the team's agents to use the new copy. > [card] [Team spaces & team agents](https://docs.dataleap.ai/share/team-spaces.md) > > Create a team, add the accounts its agents use, and move agents into it. > [card] [Templates](https://docs.dataleap.ai/share/templates.md) > > Turn an agent into a template colleagues deploy themselves. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.