Transfer and offboard

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

Where to find it:

• Connections → row actions → Manage access → the transfer icon next to Owner
• Settings → People → Members → Remove from organization (four steps)

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 is one person

Every connection is owned by exactly one member. There is no team or organization owner: transfer changes owner_user_id and nothing else.

Who can reach a connection is a separate thing — grants, made by sharing it with a member, a team, or everyone at your organization (connection:share). A transfer never adds, removes, or widens a grant, and sharing never changes the owner. That separation is deliberate: an ownership move that silently handed everyone access would be the kind of quiet widening the access model exists to prevent.

To make a personal connection into shared infrastructure, share it. To hand it to a colleague, transfer it. To do both, do both.

flowchart TD
  Start["Personal connection"] --> Why{Why change owner?}
  Why -->|Hand it to a colleague| Transfer["Transfer → another member"]
  Why -->|Others need to use it| Share["Share → member, team or everyone"]
  Why -->|Member is leaving| Offboard["Remove member"]
  Offboard --> Deleted["Their connections are deleted"]
  Deleted --> Action{Per connection}
  Action --> Replace["Pick a replacement"]
  Action --> Broken["Leave tools broken"]

Transfer a connection

1. Open Connections and find the connection.
2. Choose Manage access from its row actions.
3. Click the transfer icon next to Owner, and pick the new owner — any member of the organization except the current owner.
4. Confirm Transfer.

You'll know it worked when: the connection’s owner shows the new member, the access list is unchanged, and dependent toolboxes still run.

Transferring needs someone else in the organization to transfer to. If people beyond the new owner depend on the connection, share it with them as well — the transfer alone does not.

When someone leaves (offboarding)

Removing a member takes four short steps. Elaichi won’t let you remove someone and leave things nobody can manage.

1. Open Settings → People → Members.
2. Open the member’s menu → Remove from organization.
3. What happens. A short summary: how many things they own, how many connections will be deleted, which API tokens and AI client logins will be revoked, and which teams and roles they leave. Select Start.
4. Hand over. Choose one person or one team under Give everything to. Each thing they own (toolboxes, templates, automations, dashboards, collections, knowledge bases, apps and custom connectors) gets its own row. A row follows your choice unless you pick Someone else or Delete it. Select Next.
5. Replace connections. Their connections are always deleted. For each one, pick another connection of the same app to use instead, so the toolboxes and automations that used it keep working. Select Next.
6. Confirm. Read the summary, then select Remove with their first name.

Their connections are always deleted

A connection is someone’s own login to an app. It doesn’t become a colleague’s when its owner leaves, so removal deletes every connection the member owns, shared or not.

What you decide is what replaces it. Each connection shows what uses it (“Used by Pipeline, Weekly digest”) and a list of connections that can take its place: the same app, working, not the leaving member’s, and one you can use yourself.

If there is no other connection of that app, the step says so. Someone needs to connect one later.

Giving things to a person or a team

A team can’t own anything by itself. When you give something to a team, the team’s first admin becomes the owner and the whole team can use and edit it. A team with no admin can’t be picked; make someone on the team an admin first.

If the member owns a very large estate, Remove may finish only part of it. The work done is kept, the member stays for now, and Continue removing picks up where it stopped.

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

• Read the “Used by” line before choosing Leave tools broken.
• Transfer does not rotate credentials or re-run OAuth.
• To hand a connection to a colleague, the owner transfers it from Manage access before they leave. Offboarding never moves a connection to someone else.
• Share the systems other people depend on before someone leaves, so removal day is quiet.

Related

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