Transfer and offboard

Move a connection to a new owner without re-authorizing it, and decide what happens to someone’s personal connections when they leave the organization.

Where to find it:

• Connections → row actions → Transfer
• Members & Roles → People → Remove from organization (offboarding dialog)
• Toolboxes → share flow (nudge to transfer a personal connection to the organization)

Credentials stay in place. You’re changing who owns the connection in Elaichi, not asking the product to sign in again. Toolboxes that already use the connection keep working after a transfer.

Ownership scopes

Every connection is owned at one of three scopes:

Creating team- or org-scoped connections requires connection:create_shared. Transferring into those scopes is how a personal connection becomes shared infrastructure.

flowchart TD
  Start["Personal connection"] --> Why{Why change owner?}
  Why -->|Keep using it| Transfer["Transfer"]
  Why -->|Member is leaving| Offboard["Offboarding dialog"]
  Transfer --> Dest{New owner}
  Dest --> Org["Organization"]
  Dest --> Team["Team"]
  Dest --> Person["Another member"]
  Offboard --> Action{Per connection}
  Action --> TOrg["Transfer to org"]
  Action --> TTeam["Transfer to team"]
  Action --> TPerson["Transfer to member"]
  Action --> Delete["Delete connection"]

Transfer a connection

1. Open Connections and find the connection.
2. Choose Transfer from its row actions.
3. Pick the new owner:

4. Confirm Transfer.

You'll know it worked when: The connection’s owner column shows the organization, the team, or the new member, and dependent toolboxes still run.

Transferring to a team needs a team to exist first. Transferring to a member needs someone else in the organization. Prefer org or team ownership for anything others depend on.

Share nudge

When you share a toolbox that rides on a personal connection, Elaichi can warn you and offer Transfer to organization in one click. That keeps recipients from depending on a connection that disappears if you leave.

When someone leaves (offboarding)

Removing a member is where forgotten personal connections bite. Elaichi won’t let you delete someone and leave broken shared toolboxes behind.

1. Open Members & Roles → People.
2. Open the member’s menu → Remove from organization.
3. Elaichi loads an offboarding summary: every personal connection they own, and which toolboxes reference each one.
4. Connections used by shared toolboxes are flagged Used by shared toolboxes and list those toolbox names.
5. Choose an action per connection, then confirm Remove member.

Offboarding choices (complete list)

Defaults in the dialog

Change either before confirming. If you pick Transfer to team or Transfer to member, you must also pick the team or member — the remove button stays disabled until every row is complete.

If you try to leave a referenced connection unresolved, removal is refused (connections_need_resolution style failure). Unreferenced personal connections you delete are cleaned up with the member.

You can’t remove yourself from this screen. The last Org Owner can’t be removed until someone else is an Owner.

Good to know

• Deleting a connection breaks every toolbox and MCP server that used it. Read the “Used by” list before choosing Delete.
• Transfer does not rotate credentials or re-run OAuth.
• Offboarding only lists personal connections for the leaving member. Team- and org-owned connections stay put.
• Prefer transferring shared systems to organization or a team before someone leaves, so day-of removal is quiet.

Related

• Invite and manage people
• Organize people into teams
• Connect an account
• Manage connections