The most easily missed parts of a social media handover are often ownership, recovery email, scheduling tools and partner access, rather than passwords. This guide gives brands and agencies a practical checklist for verifying access, removing it when staff leave and finding the right person during an incident, so a document handover actually enables work.
A colleague says all accounts are in the spreadsheet, but the successor can only view data, not publish. When recovery is needed, the code goes to a disconnected private number. Usually the handover listed account names without verifying working permissions and recovery routes.
A complete handover lets the successor perform authorized tasks, removes unnecessary access from the previous owner and tells the organization how to recover during problems. The following checklist is for legitimately owned or authorized brand assets; adapt it to each platform's actual features.
Inventory assets before organizing passwords
A brand may have pages, channels, ad accounts, shops and data assets. Similar names do not necessarily mean the same managing organization. Record public links and asset identifiers visible in the dashboard, then confirm ownership to avoid choosing the wrong asset by nickname.
Keep one row per asset. Do not put passwords, verification codes, recovery codes or private messages in this ordinary handover sheet. Record only who holds them and which controlled channel provides access.
| Record | What to enter | Acceptance check |
|---|---|---|
| Asset identity | Platform, link, asset identifier, brand | Successor opens and checks it |
| Managing ownership | Organization, confirmer, basis of authorization | Responsible person confirms the record |
| Member permissions | Member identity, role, responsibility | Inspect actual assignments in the dashboard |
| Recovery methods | Custodian, update status, emergency contact | Confirm availability and organizational control |
| Connected tools | Scheduling, support, analytics, partners | Check authorization scope and responsible person |
| Outstanding content | Scheduled posts, open inquiries, disputes | Successor explicitly takes each item |
Do not infer long-term ownership from who registered first. For client projects, retain authorization and termination conditions too. When the service contract ends, follow the mutually confirmed arrangements for the handover scope and retained information.
Grant permissions by task; a successor need not become top administrator
Describe work as verifiable actions: viewing reports, answering inquiries, editing drafts, publishing and managing members. Check platform roles against each task rather than using a vague operations label in place of configuration.
Someone managing daily content does not necessarily need payment control or the ability to add administrators. Conversely, viewing statistics does not confer publishing rights. Roles differ by platform and account type; do not simply copy another platform's role names.
The UK NCSC's social media publishing security guidance recommends allowing only authorized people to publish, avoiding uncontrolled password sharing and promptly removing unnecessary access when people leave or change roles. The handover sheet should match the actual dashboard, not merely preserve a static list.
Verify the handover before the previous owner leaves
Invite the new member and have them accept, then use their own identity to enter the correct asset. Confirm they can do the intended work without accidentally opening assets outside their duties. Prefer drafts and previews for checks rather than publishing publicly or incurring real charges just to test.
For support, check access to the authorized inbox, outstanding cases and saved reply drafts. A publishing role can check drafts, materials and approval routes. Each job needs different verification; one successful login cannot replace full acceptance.
Record the verification time, participants and unresolved items. If permissions await platform confirmation, mark them incomplete and assign a temporary responsible person. Invitation sent does not mean handover complete.
Who controls the recovery email and verification devices?
Check whether recovery information remains controlled by authorized organizational personnel and who is responsible for authenticators, passkeys and backup recovery methods. Read platform setup instructions before updating anything to avoid deleting the only usable method and locking the organization out.
The NCSC's administrator account protection advice emphasizes protecting administrators, keeping recovery information current and making backups accessible if the main access route fails. This does not mean distributing every secret to all members.
Emergency contacts must also know when recovery may begin. Run a tabletop exercise: if the responsible person is temporarily unreachable, who finds ownership records, who approves recovery and who contacts the platform? No actual password reset or consumption of one-time recovery codes is needed.
Hand over scheduling tools, agency authorizations and browser sessions too
Outside the member list, scheduling, third-party support, analytics and agency relationships may still retain access. List these connections separately and confirm the successor can manage them, their scope remains necessary and someone owns renewal or expiry.
If your team maintains browser environments by brand, learn about member permissions and environment groups on the PurpleMark website. Assign the brand's environment to the successor and check its name, responsible person and access scope so the work entry point moves with the role.
Environment access, platform roles and third-party authorizations are separate checks. Removing one still requires inspecting the others. Deleting a desktop shortcut is not completed revocation, and exported session files should not be distributed as ordinary documents.
Check the outcome after removing access
At the agreed switch time, someone retaining administrative rights should remove departing members and unused partner authorizations. If credentials were shared, update them in a platform-supported way and check active sessions and connected apps, while avoiding interruption of necessary ongoing work.
Record specific results, such as a member removed from a particular page role or a scheduling connection revoked, rather than merely ticking security handled. Where screenshots are needed, mask personal data, email addresses and other sensitive information, and store them in a controlled location.
For any entry point not yet revoked, record the reason, handler and follow-up time. It remains a task even after the previous owner has left; do not delete it from the checklist.
Keep the checklist useful after handover
Update it whenever accounts, contractors, roles or tools change. Periodic reviews should focus on people still needing access, finished projects and assets without an owner, rather than just counting accounts.
Content schedules, material approval and performance reviews can have their own daily plan. The handover checklist answers who owns assets, who can do what and whom to contact when something goes wrong. Linking these records lets the successor turn permissions into continuous work.
Completion has concrete criteria: the successor can perform authorized tasks, old access has been removed within the agreed scope, recovery responsibility is clear and unresolved items have an owner. Meeting them prevents accounts from losing control when a colleague leaves.


