What to document when a store administrator changes
A store administrator leaves. Then the team finds out that their personal email owns the app account, the domain contact and a spreadsheet full of product rules.
Suddenly the handover is a hunt through old messages and memory. It’s a bit like finding out the only key to the stockroom went home in someone’s pocket. Documenting an administrator change is about passing on ownership and decisions, not just a list of logins.
Identify the systems in scope
List everything the administrator managed: storefront, domain registrar, hosting, email, analytics, product feeds, payment tools, apps, support channels and shared files. Confirm which are really in use. Removing their store account doesn’t transfer ownership of connected services.
For each system, record the current owner, incoming owner, access method, billing responsibility and any recovery contact. Keep passwords, tokens and recovery codes in an approved secret manager or service. The transition document should say where access is managed, not expose the secret itself.
Capture responsibilities and decisions
When I take over a client’s store, the first thing I ask is who gets the renewal emails. It sounds boring, but it finds hidden dependencies faster than anything else. Then list the recurring tasks: product publication, app updates, access approvals, renewals, reporting and imports. Note the schedule and what can go wrong. A vague list of duties won’t tell the new owner where to begin.
Record important decisions and their reasons. A search rule, shipping exception or app configuration may look arbitrary without the context behind it. Identify which decisions are approved policy, which are temporary workarounds and which remain unresolved.
Transfer access safely
Use individual accounts and the platform’s own ownership transfer process. Check the incoming administrator can get into everything before you remove the outgoing person. A new administrator may need broad access for a while, but shouldn’t inherit every permission for good.
Remove old access through the appropriate workflow once ownership is confirmed. Consider API keys, app connections, recovery email addresses and shared devices. A user list on one platform does not represent all access paths. Coordinate with IT or service owners for identity and security controls.
Keep operations running
Set a transition date and list what must happen during it, such as a scheduled import, a renewal or a campaign update. Name a backup owner for critical processes. If a service relies on the departing person’s personal account, move ownership before that account is disabled.
Test the incoming owner’s ability to perform key tasks: publish a product, view a report, contact support or restore a configuration using the approved process. Do not run a real transaction or expose customer data just to prove access. Use documented safe tests where available.
Handle unresolved knowledge
Ask the outgoing administrator about brittle steps, known issues, vendor contacts and assumptions. Separate tested facts from things remembered. If nobody understands something, assign an investigation instead of writing it up as settled procedure.
Protect customer and commercial information during the transition. Share only what the new role needs, and follow the organisation’s retention and privacy policies. Do not copy a personal inbox or private message history wholesale into a shared folder.
Confirm closure
Keep a checklist with system, owner, transfer status, verification and date. After the change, review access and confirm that the new owner receives alerts. Archive the handover in the approved location and set a review date for temporary privileges or incomplete items.
Draw the ownership chain
Write down which business account controls the store, which people can manage access and which external accounts support it. Include domain registration, billing, app subscriptions and notification addresses where they affect day-to-day operation.
The aim is to locate responsibility, not collect secrets into a document. Refer to the approved password manager or account recovery process instead of pasting credentials beside the account list. A handover folder should not become the easiest way into the business.
A personal email address deserves particular attention. It may receive renewal notices or recovery messages even when everyone else can use the store normally. Confirm the supported transfer route with the provider and complete it while the outgoing person is available.
Record decisions that still need a person
An administrator often holds context that is absent from the dashboard: why an app remains installed, which supplier file is trusted, why a product is hidden or who approves refunds outside the normal process. Ask for these decisions explicitly.
I’d separate established policy from a one-off workaround. The next administrator needs to know whether they are inheriting a rule or merely a convenient habit. Otherwise a temporary exception can survive for years because nobody knows they are allowed to question it.
Include unfinished work and the next commitment. A renewal due soon, an unresolved data problem or an awaiting approval should have an owner after the handover. “The team knows about it” is too vague to rely on.
Prove that the new owner can recover access
Normal login is only one part of continuity. Check that the incoming administrator understands recovery contacts and can reach the provider’s support route where necessary. Do not perform disruptive recovery tests casually; review the documented mechanism and use the provider’s supported checks.
Then remove access that has genuinely ended and confirm that essential notifications still reach the business. Record the completion of the transfer. Changing the name in an organisation chart does not finish the job if the store still depends on the previous administrator’s inbox.
Related reading
A clean administrator change leaves the store with clear ownership and fewer hidden dependencies. Which service or decision would be hardest to recover if your current administrator left tomorrow?