Transfer codes to another account

An asset belongs to its workspace, and moving it to a folder does not transfer ownership to another account. The current user center has no general account-transfer button that moves existing codes and all their history.

Identify the source account, source workspace and intended destination workspace. Record asset IDs and printed public links before asking for assistance. Control of the original domain and path matters: an image alone cannot authorize takeover of a code operated by another provider or person.

Use Contact us to explain the business change and desired scope. Do not send either account's password or secret keys. A request must be assessed rather than treated as an automatically completed transfer; owners cannot be changed through an ordinary member-role edit.

If ongoing collaboration is enough, an authorized owner or administrator may add an existing registered member to the original workspace, subject to plan limits. This grants that role's access without moving ownership. Creating a new code instead requires distributing its new image; it cannot silently reuse a reserved old slug.