Run the account handover workflow

This guide shows you how to hand your admin account over to a successor. Use it when you leave or step out of your role.

Who can do this: Admins who have permission to run account handovers. Org owners can do this by default. A handover always hands over your own admin account.

Before you start

Pick a successor who is already an active admin in your organization.
Know what the handover does. It moves the roles assigned directly to you to the successor. It archives your admin account, so you can no longer sign in as an admin. Roles you get through a group binding are not moved, and a direct role whose expiry date has already passed is not moved either.
If you are this organization’s only Org Owner and you hold that role only through a group binding, give the successor the Org Owner role directly first. Otherwise the handover fails, because it would leave the organization without an Org Owner.
Starting a handover needs a recent sign-in. If you signed in a while ago, you’ll be asked to sign in again when you click Complete handover.
Records are not reassigned. Your events, saved searches, saved reports and integrations stay as they are.

Steps

Step 1 — Open the wizard

Go to Admins (at /admin/admin-security/admins). (The Admin & Security sidebar link has no page of its own yet.)
Open the ⋮ menu on any admin row and select Account handover. The wizard opens at “Step 1: Choose a successor”.

Step 2 — Choose a successor

Keep Choose an existing admin selected.
In Select successor, choose the admin who is taking over. The list shows only other active admins.
Click Next.

Step 3 — Transfer scope

Review the four checkboxes: Events, Saved searches, Saved reports and Integrations. All are checked by default.
Uncheck any you want. Your choice is saved with the handover, but this version doesn’t reassign records: they stay as they are either way.
Click Next.

Step 4 — Review and complete

Check the successor’s name on “Step 3: Review and complete”.
Click Complete handover.
If a Confirm it’s you box opens, your sign-in is too old for this step. Confirm your identity: you sign in again and come back to Step 1 of the wizard. Choose the successor and transfer scope again, then click Complete handover.

The page then says “Handover in progress — you can navigate away.” You can leave the page.

Verify

You’ll know it worked when:

On the Handovers list (/admin/admin-security/handovers), the handover’s badge reads Complete.
The successor holds each role that was assigned directly to you: their own assignment where it already covered yours, otherwise an exact copy of yours. A role the handover’s card lists as not transferred is the exception: the successor keeps their own assignment of it, and yours wasn’t moved.
You and the successor each receive a confirmation email. It names the roles that moved and any that weren’t transferred, and says your admin account was archived.
Your account shows Handover complete on the Admins list, and you can no longer sign in as an admin.

If something goes wrong

“A handover is already active for this admin” — You already have a handover that hasn’t finished. Open the Handovers list to see it.
“Starting this handover needs a more recent sign-in.” — You closed the Confirm it’s you box without signing in again. Nothing was started. Click Confirm your identity to sign in again, then repeat the steps.
“Your admin identity couldn’t be read, so the handover can’t start. Reload the page to try again.” — The page couldn’t read which admin account is yours, so it doesn’t show the wizard. Reload the page.
“Handover job failed” on the Handovers list — The banner says exactly why, for example that the successor’s account is suspended. Nothing was transferred, and your account is unchanged. Click Retry to start a new handover with the same successor and choices, or start a new one with a different successor. See Handover job failed.
The card lists a role as not transferred — The successor already held that role, and neither assignment covers the other: neither has both the same or a wider data scope and an end date at least as late (no end date counts as the latest). Their own assignment was left exactly as it was, and yours wasn’t moved. The card’s sentence says which part of each assignment the other doesn’t cover — how many membership levels, tags or event categories one includes and the other doesn’t (it gives the number, not their names), and which one ends earlier — and ends one of two ways (shown here for a successor named Jordan Successor and the Finance Manager role). If Jordan Successor’s data scope doesn’t cover yours, or one of the two data scopes can’t be read, it ends “An Org Owner can change Jordan Successor’s existing assignment of Finance Manager (its data scope; its end date can’t be changed in the app yet).” If it already covers yours (the same or wider), it ends “Jordan Successor’s data scope for Finance Manager already covers the outgoing admin’s, and the app cannot change the rest yet: an assignment’s end date can’t be changed and a role assignment can’t be removed in the app.” Assigning the role to the successor again doesn’t work, because they already hold it. Where the successor’s data scope doesn’t cover yours, an Org Owner can change the data scope of the successor’s assignment with Configure data scope on the successor’s Roles tab — see Create a custom role. Changing an assignment’s end date, or removing a single role from an admin, isn’t available in the app yet, so when the successor’s data scope already covers yours, the gap can’t be closed in the app. (When one assignment covers the other, nothing is listed: the successor keeps theirs if it covers yours, or gets an exact copy of yours if yours covers theirs.)
You chose “Invite a new person” — Step 3 reads “Review and stage” and the button is Stage handover: it only saves the handover as staged. No roles move, your account stays active and no email is sent. This version doesn’t send an invitation email, and the invitation can’t be accepted yet, so a staged handover doesn’t finish. Hand over to an existing active admin instead.
“An admin or pending admin invitation with this email already exists” — The email you entered for the new person already belongs to an admin or to a pending admin invitation. If they’re an active admin, go back to Step 1 and choose them under Choose an existing admin.