# Transfer ownership and offboard members without orphans

> Owners can hand any workflow, app, skill, project, or credential to another member, and deactivating someone transfers or deletes what they own.

Sep 15, 2026. Topics: Collaboration. https://www.generalinput.com/changelog/2026-09-15-ownership-transfer

Every resource in a workspace can now change hands, and deactivating a member can no longer strand what they built. An owner can give a workflow, app, skill, project, credential, database, store, or browser to any active member. When someone leaves, an admin moves everything they own to a successor, or deletes it, in the same step as the deactivation.

### How it works

- **Three kinds of move.** A transfer gives one resource away, a handoff moves everything a member owns to a successor, and an adopt lets an admin take over resources whose owner is already inactive.
- **Workflows move with their wiring decided.** For each connection the giver owns, they choose share or disconnect. Transfer stays disabled until every choice is made, because a workflow wired to something its new owner can't see breaks on its first run.
- **Projects move with their contents**, with a preview of what will move. Other members' resources in the project stay theirs.
- **No lost races.** Every owner change checks the expected current owner first.
- **Deactivation takes a policy.** Transfer everything, delete everything, or neither only when the member owns nothing, all in one transaction.

### Sharing surfaces

- Every resource names its owner, and sharing reads as Private or Shared.
- Controls you can't use are disabled with a tooltip that says why, never hidden.

### Also shipped

- Enable or disable a workflow or skill from the agent, the API, or `geni resource enable`.