Transfer and offboard

Move a connection to a new owner without signing in to the app again, and decide what happens to a member's items when you remove them from the organization.

Where to find it:

• To transfer: Connections → the row's actions menu → Manage access → Transfer ownership…
• To offboard: Settings → People → Members → the member's actions menu → Remove from organization

Before you start

Elaichi disables Remove from organization with a reason when the member's role outranks yours. You cannot remove yourself from this screen. The last Org Owner cannot be removed until another member is an owner.

How ownership and access differ

Every connection has exactly one owner, a member. A team or the organization cannot own a connection.

Who can reach a connection is a separate list of grants. You make a grant by sharing the connection with a member, a team, or everyone in your organization. A transfer never adds, removes or widens a grant, and sharing never changes the owner.

To hand a connection to a colleague, transfer it. To let others use it, share it. To do both, do both.

flowchart TD
  Start["A personal connection"] --> Why{"What do you need?"}
  Why -->|"Hand it to a colleague"| Transfer["Transfer to another member"]
  Why -->|"Others need to use it"| Share["Share with a member, a team or everyone"]
  Why -->|"The owner is leaving"| Offboard["Remove the member"]
  Offboard --> Deleted["Their connections are deleted"]
  Deleted --> Choice{"For each connection"}
  Choice --> Replace["Pick a replacement connection"]
  Choice --> Broken["Leave its tools broken"]

In words: a transfer gives one connection to one colleague, sharing gives others access, and removing a member always deletes that member's connections. When you remove a member, you choose a replacement connection for each one, or you let its tools stop.

Transfer a connection

1. Open Connections and find the connection.
2. Open the row's actions menu and choose Manage access.
3. Choose Transfer ownership….
4. Under New owner, pick any other member of the organization.
5. Leave Keep my access selected if you still need to run the connection's tools. Clear it to give up all access.
6. Choose Transfer ownership.

The connection's owner changes to the new member, the list of grants stays the same, and the toolboxes that use the connection keep working. Elaichi does not rotate credentials or run the app's sign-in again.

If Transfer ownership… is disabled, nobody else is in the organization yet. Invite someone first.

If others beyond the new owner depend on the connection, share it with them too. A transfer alone does not.

Remove a member and hand over their items

Removing a member takes up to four steps. Elaichi will not let you remove someone and leave items that nobody can manage.

1. Open Settings → People → Members.
2. Open the member's actions menu and choose Remove from organization.
3. What happens. Read the summary of what the member owns, which connections are deleted, which API tokens and AI client logins are revoked, and which teams and roles they leave. Choose Start.
4. Hand over. Choose a person or a team under Give everything to. For each kind of item, accept that choice, choose Someone else…, or choose Delete them. Choose Next.
5. Replace connections. This step appears only when the member owns connections. For each app, choose a replacement for each connection, or Leave tools broken. Choose Next.
6. Confirm. Read the summary, then choose Remove followed by the member's first name.

The member loses access to the organization right away, and Elaichi applies every choice you made.

What happens to their connections

Removing a member always deletes every connection that member owns, shared or not. A connection is the member's own sign-in to an app, so it does not become a colleague's when the member leaves.

What you choose is what replaces it. For each connection, the Replace connections step shows what uses it (the Used by column) and a list of replacement connections. A replacement is a working connection to the same app that is not the leaving member's and that you can use yourself.

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

What happens to their other items

You hand the member's other items to a person or a team, or you delete them. A team cannot own anything by itself. When you give something to a team, the team's first administrator becomes the owner, and the whole team can use and edit it. You cannot pick a team that has no administrator. Make someone on the team an administrator first.

Elaichi may list other kinds of items the member owns. They follow the same choices.

If a member owns a very large number of items, Remove may finish only part of the work. Elaichi keeps the work it did, the member stays for now, and Continue removing picks up where it stopped.

What to know

• To keep a connection for a colleague, the owner transfers it from Manage access before they leave. Offboarding never moves a connection to someone else.
• Share the connections other people depend on before someone leaves, so the day you remove them stays quiet.
• Elaichi revokes the member's API tokens and AI client logins when you remove them.

Related

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