What should I review before handing an online account to a new owner?

Start with permission, not passwords. Check the service’s own current rules for whether ownership can be transferred and what process it requires. Don’t assume that an account can be handed to someone else just because you can sign in. If transfer is not allowed or the instructions are unclear, pause and ask the service or the organization’s account administrator for an authorized route.

Next, list what the account includes: the account itself, any team or organization membership, administrative roles, billing control, and access to related work. These may not all move together. For example, Dropbox DocSend says that for its team accounts the owner has admin privileges and billing access; when ownership is transferred, the former owner becomes a member and loses access to billing information. That example applies specifically to DocSend team accounts, not other services or ordinary personal accounts. [S1]

Assumption for the rest of this guide: you have authority to arrange the handoff, and the service permits it.

Make a small handoff map before changing anything. For each item, record the current holder, intended holder, and how you will verify the change:

1. Ownership: Is there an official ownership-transfer control, or does an administrator need to make the change?
2. Roles: Which admin, member, or other roles will each person have afterward? Does your own role change?
3. Memberships: Are there teams, shared spaces, or groups attached to the account? Check each one rather than assuming it follows ownership.
4. Billing: Who is responsible for billing access or decisions after the handoff? Confirm what the service’s rules say; don’t infer this from another platform.
5. Work access: Which files, settings, or ongoing tasks does the successor need? Note anything that requires a separate authorized change.

Write down uncertainties as questions for the service administrator or support team. The DocSend example illustrates why roles and billing deserve separate checks, but it does not establish how any other service handles them. [S1]

Review the account’s profile and settings for information that identifies you personally or would confuse the next owner. Depending on the service, that might include a display name, profile image, contact details, biography, notification preferences, or saved preferences. Treat these as things to inspect, not as a guaranteed list of settings every account has.

Decide with the successor which details should be removed, replaced with the organization’s approved information, or left unchanged for continuity. Don’t remove records or work materials just to make the account look clean; first confirm what should be retained and who is authorized to decide. If a detail cannot be edited, record it as an unresolved handoff item and ask the administrator what to do.

Keep a brief before-and-after note of the intended changes. Avoid putting passwords or sensitive personal data in a general handoff document.

Use this copyable note, filling in only details you are authorized to share:

“Account: [service and account name] Transfer permission checked: [where/how confirmed] New owner: [name or role] Handoff date: [date] Ownership change: [official steps or administrator responsible] Roles after handoff: [person — intended role] Memberships/shared areas to check: [list or none identified] Billing responsibility/access: [confirmed arrangement or question to resolve] Profile details to update or remove: [items] Work or settings needing separate action: [items] Still unresolved: [questions and responsible person] Completion check: [how the new owner will confirm access] My access afterward: [expected change, confirmed with service]

Before you send it, remove anything the recipient does not need. Keep the handoff conditional until the service-approved ownership change is complete. The exact controls and effects depend on the service; the cited DocSend details should not be treated as general transfer instructions. [S1]”