Know what the business owns
A social account can be an important route for customers to recognise a business, ask questions and find current information. Begin by listing the accounts and associated assets that the business uses, including the page or profile, the responsible owner and the email or recovery route attached to it. Keep the inventory in an appropriate secure location.
Check whether the business controls the account or relies on an individual’s personal login. An agency or departing employee may legitimately help manage a page, but the business should know how it retains ownership and regains access. Do not publish the inventory or store recovery codes in an open content calendar.
Protect sign-in and recovery
Use a strong, unique password for each account and consider a reputable password manager. Enable two-step verification where available and follow the National Cyber Security Centre’s current advice. Protect the associated email account too: a weak recovery route can undermine an otherwise well-protected social profile.
Store recovery information securely and know which authorised person can use it if the primary account holder is unavailable. Test the documented recovery process without exposing a code or credential to a colleague who does not need it. Platform options change, so confirm the controls available for the actual account.
Give each person appropriate access
Where the platform supports named roles or delegated access, assign only the permissions needed for the work. A person writing drafts may not need authority to change ownership or payment settings. Record who approved the access, what it covers and when it should be reviewed.
Avoid sending a shared password around a team or giving a supplier unnecessary control simply because it is convenient. If a platform requires a particular access method, check its official guidance and agree an arrangement that keeps ownership and recovery with authorised business representatives.
Account control in four checks
- OwnRecord the account and owner
- ProtectUse strong sign-in and recovery
- LimitGive only necessary access
- ReviewRemove access when roles change
Recognise suspicious requests
Be cautious of messages claiming that an account will be deleted unless someone clicks an unfamiliar link or shares a code. Attackers can imitate platform notices and pressure people to act quickly. Use a known route to open the platform directly and verify the issue rather than following an unexpected message.
Never disclose a password or one-time code to a supposed support contact through a social message. If a person has already interacted with a suspicious request, follow your incident process promptly: secure affected accounts, review access and seek appropriate technical help. Do not conceal the issue because it feels embarrassing.
Plan a safe supplier handover
Before work begins, agree which assets a social-media supplier needs and who owns them. Record the permissions, the work included and the process for ending access. Make sure that content approvals, image licences and account recovery remain understandable if the person managing the work changes.
At handover, remove access that is no longer needed, review connected applications and confirm that an authorised person can still sign in. Revoke or rotate credentials when appropriate and check the recovery route. Preserve necessary business records without transferring private messages or personal data unnecessarily.
Example: changing a social-media manager
Imagine a small business appoints a new social-media manager. The owner confirms which business page and profile are in scope, grants the relevant role and records the agreed responsibilities. Before the old manager’s access ends, the team confirms that scheduled content and approved image files are available to the business.
Once the handover is complete, the owner removes the old access and reviews connected tools. This example is illustrative; it does not describe an actual account or supplier. The appropriate settings depend on the platform and the roles it currently supports.
Review regularly and after changes
Set a manageable review date for account owners, access, recovery methods and connected applications. Check again when someone leaves, a device is lost or a supplier relationship ends. Make sure contact details, public links and the person monitoring messages are current as well as the security settings.
A secure account should remain usable by the authorised team. Overly complicated arrangements that no one understands can create their own risk, so keep clear instructions in a restricted place and practise the handover before an emergency occurs.
Write a recovery plan before it is needed
Choose at least one authorised person who can initiate recovery if the normal manager is unavailable. Document the official route to the platform’s help and the approved location of recovery information, but do not put passwords or one-time codes in the plan itself. Check that the associated email account is controlled by the business and protected with appropriate sign-in security.
Decide how the team will communicate if a profile appears compromised. For example, a named owner can use the official recovery process, tell the relevant colleague, and review connected applications and scheduled content. If a suspicious message has been sent to customers, the business should assess what happened and obtain suitable advice about notification and data-protection obligations where relevant.
Practise locating the plan without triggering a real reset or sharing a recovery code. Update it when an owner, device, email address or supplier changes. A documented process should be accessible to the right people at the right time and restricted from everyone else; an abandoned document in a former employee’s account will not provide reliable control.
Keep the ownership and recovery review separate from the everyday editorial calendar. The latter may be shared with freelancers who need to see draft captions but should not see account recovery information. Review connected third-party publishing tools as well as the platform’s own roles, because a tool may retain access after an individual stops working on the account. Remove access through the official interface and confirm that the business can still publish and recover the profile.
A practical account checklist
List the profile, owner, authorised managers, recovery route and review date. Confirm strong sign-in, appropriate two-step verification and a way to remove access. Check that financial or advertising permissions are separately controlled where relevant, and train the team to recognise suspicious messages.
Use current official platform and NCSC guidance for the actual configuration. This article is a practical starting point rather than a guarantee against compromise; the right controls depend on the services and risks involved.
