Transfer Ownership of AI Agents Before Someone Moves On

Transferring ownership of an AI agent is handing its OWNER role, with every permission that comes with it, to someone else. In Insulin it works only while the current owner is still an organization ADMIN, so a handover has to start before the owner’s role changes.

---

Someone who built your team’s shared agents, apps and channels is changing roles or leaving. Whoever runs the handover has two questions: how does their work move to someone else, and what can an admin reach if it doesn’t? Insulin’s documentation answers both for the case it covers, a handover made while the person is still in the organization, and the answer turns on the order you do things in. For the roles themselves, day to day, see who can run what in an AI workspace.

Which Insulin resources can change owners?

Organization agents, Custom Apps, channels and knowledge bases can; personal agents, apps and channels cannot; and the docs describe no transfer for a job. Wherever a transfer exists, only the resource’s current owner can start it.

Resource	Transferable?	Who can receive it	What the former owner keeps	Without a share, an org ADMIN can’t…
Organization agent	Yes, by its owner while they are an org ADMIN	An org ADMIN	USER: use it, not edit it	manage its sharing (that takes ADMIN on the agent)
Organization Custom App	Yes, by its owner while they are an org ADMIN	Another org ADMIN	Admin: edit it, manage its sharing, delete it	delete it (that takes ownership or an Admin share)
Organization channel	Yes, by its owner; both owners must be org ADMINs	An org ADMIN, added as a member if needed	Not stated in the docs	reach it: access comes from membership or org-wide sharing
Organization knowledge base	Yes, by its owner	Any other active member	Not stated in the docs	open it
Job	No transfer is documented	—	It stays theirs	see, run, edit or delete it
Personal agent, app or channel	No	—	It stays theirs	reach it: it is private to its creator
Personal knowledge base	No transfer is documented	—	It stays theirs	open it

Two different roles are called admin here. The org ADMIN role is set per person across the organization: it lets someone create organization resources and manage organization settings, and it is the role agent, app and channel transfers check. ADMIN on a resource is a share on one agent, app, channel or knowledge base: managing that resource’s sharing depends on it, and on an app or a knowledge base, so does deleting it. Holding the first does not grant the second.

Why must the transfer happen before the role change?

Because the transfer is refused once the owner is no longer an org ADMIN, and nobody else can make it for them. The Agents documentation is direct: “If you are no longer an organization ADMIN yourself, the transfer is refused, and the message says why.” The Custom Apps page says the same, and a channel transfer needs both owners to be organization administrators.

Nobody can step in because the transfer is the owner’s alone: an agent’s Share dialog shows Transfer ownership “to the owner and to no one else”, and apps and channels follow the same owner-only rule. And every owner of an organization agent, app or channel held the org ADMIN role when they created or received it, since only an org ADMIN can create one and a transfer can only go to one. Change that role first, and the handover is blocked.

So: transfer first, change the role last. If your offboarding process lowers a leaver’s role the day they give notice, move the Insulin handover ahead of that step. Knowledge bases follow a different rule, covered below.

How do you transfer each resource?

Agents and Custom Apps transfer from their Share dialogs; channels and knowledge bases follow rules of their own. Only the owner can start any of them.

An organization agent

An organization agent goes to an org ADMIN, and its former owner drops to USER. From the agent’s settings:

1. Click Share.
2. Click Transfer ownership next to the Owner row.
3. Choose the new owner from Select new owner…, which lists organization ADMINs only.
4. Click Transfer.

The new owner receives full ownership and control. The former owner can still use the agent but no longer edit it; if they should keep editing, the new owner grants them EDITOR or higher. An organization agent can use organization-level integrations only, so none of its connections were the former owner’s personal ones. Personal agents cannot be shared or transferred, and their Share button is disabled.

An organization Custom App

An organization app goes to another org ADMIN, and its former owner keeps Admin. In the app’s Share App dialog:

1. Click Transfer ownership beside the Owner row.
2. Pick the new owner from Select new owner…, which lists organization ADMINs other than you.
3. Click Transfer.

Keeping Admin means the former owner can still edit the app, manage its sharing and delete it: useful for a builder changing teams, and access to review for someone leaving.

To delete an organization app, an org ADMIN who does not own it needs an Admin share on it; the org role does not count by itself. Like an organization agent, an organization app acts through the organization’s connected accounts, not its owner’s. A personal app has no Owner row and cannot be transferred.

An organization channel

An organization channel goes to an org ADMIN, and both the current and the new owner must be organization administrators. The new owner does not need to be a member already; they are added automatically. Transfer is available on organization channels only, so a personal channel stays with its creator.

• The owner cannot leave until they transfer. Any other member can leave a channel they no longer need.
• Org admins do not automatically become channel admins. Access comes from explicit membership or org-wide sharing, so the org role alone does not let anyone manage a channel.

The Channels documentation does not say what role the former owner keeps, so check the Members panel afterwards. The transfer moves no jobs, either: a channel owns none, and its Jobs tab lists the jobs of its member agents that you are allowed to see.

An organization knowledge base

An organization knowledge base can go to any other active member of the organization, not only to an admin. Only its owner can transfer it: a knowledge-base Admin can delete it and manage its sharing, but not hand it on.

Even an organization admin cannot open an org knowledge base they were not shared on. Access comes only from a per-knowledge-base share or org-wide sharing; the org ADMIN role is needed to create one, not to open it. A new organization knowledge base is visible only to its owner, so one that was never shared is reachable by nobody else. Transfer it to whoever will maintain its content, or share it, while the owner is still here.

The documentation does not say what role the former owner keeps. A personal knowledge base has no documented transfer, and even organization admins cannot open it unless it is shared with them.

Can a job be handed over?

The docs describe no way to transfer a job, and a job is private to the person who created it. Only its owner can see it, run it, edit it or delete it, organization administrators included, so the person moving on is the only one who can even list their jobs.

A job also runs within its creator’s scope: its agent has access to the same resources and integrations that the creator has. The practical handover is therefore a re-creation, done while the owner is still around to read their jobs out:

1. The owner goes through their list in the Jobs app. Each job’s page shows its trigger and its instructions, plus the expression for a cron job, or the source and filter for a push job.
2. Someone who stays creates each job the team still needs. The Jobs app has no create form: ask the assistant in chat, or use POST /jobs over the REST API. How to schedule a recurring AI agent job walks through it.
3. Test the replacement. It runs within its new creator’s scope, which may not reach everything the original did. Run now fires a cron or push job immediately, as if its schedule or event had arrived.
4. The owner switches the original off with its Enable / Disable switch, or deletes it, so the work doesn’t run twice.

What order should a handover follow?

Work through the owner’s resources while they still hold their org role, and change that role last. In order:

1. List what they own, from their side. Nobody else can see their jobs, or an organization knowledge base they never shared; a resource’s settings badge reads Owner when it is theirs.
2. Transfer the agents, apps and channels to an org ADMIN while the owner is still one too.
3. Transfer each organization knowledge base to whoever will maintain it, or share it.
4. Re-create the jobs the team still needs, then switch the originals off.
5. Rebuild what the team relies on in a personal agent, app or channel as an organization resource, which only an org ADMIN can create.
6. Review what the former owner keeps: USER on each agent, Admin on each app, and whatever each channel’s Members panel shows. The new owner now manages sharing, so they decide whether that access stays.
7. Change the person’s org role last.

Frequently asked questions

Who can receive ownership of an AI agent in Insulin?

Only someone who is currently an organization ADMIN, and only for an organization agent. The owner picks the new owner from a list that shows org ADMINs alone. A personal agent cannot change hands, and its Share button is disabled.

What does the former owner keep after a transfer?

An agent’s former owner drops to USER and needs EDITOR or higher from the new owner to keep editing. A Custom App’s former owner keeps Admin, so they can still edit it, manage its sharing and delete it. The docs don’t say for channels or knowledge bases.

Why was an ownership transfer refused?

An agent or Custom App transfer is refused when the owner is no longer an organization ADMIN, and the message says why. Only the owner can start a transfer, so an org admin cannot make it on their behalf.

Can an org admin open a knowledge base nobody shared with them?

No. Access to an organization knowledge base comes only from a per-knowledge-base share or org-wide sharing; the org admin role alone does not grant it. Its owner can transfer it to any other active member of the organization.

Can a job be transferred to someone else?

The documentation describes no way to transfer a job. A job is visible only to the person who created it, organization administrators included, so its owner lists their jobs and a teammate who stays creates the ones still needed.

Do org admins automatically get access to organization channels?

No. Org admins do not automatically become channel admins; access comes from channel membership or org-wide sharing. A channel transfer needs both the current and the new owner to be organization administrators, and the owner cannot leave until they transfer it.

Takeaways

• Organization agents, apps, channels and knowledge bases change hands; personal agents, apps and channels don’t.
• Agents, apps and channels go to an org ADMIN, and the transfer is refused once the owner isn’t one. Transfer first; change the role last.
• The former owner drops to USER on an agent and keeps Admin on an app.
• Without a share, an org ADMIN can’t open an organization knowledge base, isn’t automatically a channel admin, and can’t see anyone else’s jobs.
• The docs describe no transfer for a job: its owner lists them, and someone who stays re-creates the ones still needed.

Ownership is one stage of governing an agent over its whole life; AI agent lifecycle management covers the rest, from request to retirement. For what AI agents in Insulin can do for a team, start with the product page; the Insulin roles and permissions reference is the model every rule above sits on.