Hand a workspace to its next owner

Open Workspaces → Ownership handoff. The current owner can offer ownership to a teammate who already has approved private workspace access and a verified account. That exact teammate signs in, opens the same page, reviews the offer, and explicitly accepts or declines.

What changes when they accept

The receiving teammate becomes the owner. The previous owner becomes an administrator and retains access until they choose to leave or the new owner removes it. Both existing operator enrollments remain the same, so a handoff does not silently add a paid seat. For a professional workspace, first approve the receiving person’s operator seat through People & access. Couple workspaces retain their free access rules.

The business workspace itself does not move or get recreated. Its client records, projects, shared-wedding participation, signed documents, invoice history, gallery orders and existing URLs remain in place. Connected provider accounts also remain attached. Changing app ownership is separate from legal ownership and administrator settings held by payment, email, or fulfillment providers.

For example, a studio owner can hand the business to their existing studio administrator without copying client contracts or moving individual weddings. After the administrator accepts, the previous owner can use Leave this workspace when the transition is finished.

Keep the agreement current

An offer expires after one to fourteen days. Making another offer cancels the earlier pending one. The owner can cancel a pending offer; the receiving teammate can decline it. If the reviewed ownership or either party’s permissions change, acceptance stops and the current owner must make a fresh offer. A successful handoff remains in the private history with its original note and decision time.

An interrupted response can be checked using the original request. The operation cannot create a second handoff or accept one twice. Removed members and anonymous integration keys cannot approve or reveal ownership records. The versioned account-only interface is /api/v1/workspaces/ownership.

Before leaving

Review scheduled work that relies on your personal approval or connected account. Existing job families recheck their required authority; the new owner should review holds and reconnect any personally owned provider connections as appropriate. Removing a person does not delete the business’s documents or financial history. If the original owner cannot sign in, use the account-recovery process; the app does not let another administrator self-promote around a missing owner.

The additive ownership-history migration is applied during coordinated setup. It retains explicit role transitions and disables the old migration-only owner identity shortcut after an accepted handoff, so signing back in cannot silently restore former ownership.