hello@wpfoss.com
PasswordsStaff SecurityOffboardingHeylogin

What to do when an employee leaves: the password checklist

When someone leaves, switching off their email is not enough. A plain checklist of the logins to change, the order to do it in, and how to stop it happening again.

By WPfoss Team

A member of staff hands in their notice, or is let go. You switch off their email and collect the laptop. It feels finished.

It is not. They still know the password to the company bank portal, the domain account, the website login, and the social media pages. Taking away their email does not change any of those. This guide is a plain checklist for what to change when someone leaves, in what order, and how to make the next time painless.

Why removing their account is not enough

A login has two parts: a way in, and the knowledge of the password. Switching off a person’s own account removes the first. It does nothing about the shared logins they used to do their job.

The UK’s National Cyber Security Centre (NCSC) states the rule plainly: if someone is no longer allowed access to a shared password, the password should be changed. The NCSC also lists an effective movers and leavers process as part of good password practice. In other words, this is not extra caution. It is the basic expectation.

Most leavers are not a threat. But you cannot know that, and a former employee’s old phone, a shared chat history or a note in a browser can leak a password long after they have gone. Changing it costs minutes. Not changing it can cost you the business account.

Before the last day: make the list

You cannot change what you cannot list. Do this first, ideally while the person is still there and can help.

  1. Ask the person, and their manager, which accounts they used. Include the ones nobody thinks about: the domain registrar, website hosting, the website admin area, email marketing, the accounting package, advertising accounts and the company social media pages.
  2. Check where logins are kept. A shared spreadsheet, a chat thread, a notes app or a browser saved password counts. Anything they could open, they may have copied.
  3. Note who receives the security codes. If the second step on an account sends a code to their personal phone, you need to move it before they go, or you may be locked out.
  4. Decide who takes over each account. Every shared login needs a named owner afterwards.

On the day: the order that matters

Work from the accounts that can hurt most, down to the ones that can hurt least.

  1. Money first. Bank, payment providers and anything that can send or approve payments.
  2. Email and the domain. Whoever controls your email and your domain registrar can reset almost every other password and can take your website and email offline. Change these early.
  3. Website and hosting. Change the hosting login and the website admin password. Remove the person’s own admin user from the website as well, and look at the list of users for any accounts you do not recognise.
  4. Customer and business systems. Accounting, the customer list, shared drives, project tools.
  5. Social media and advertising accounts. These are often taken over and used to message your customers, so do not leave them for last week.
  6. Everything else, including the tools that were only ever used by that person.

For each one, do three things: change the password to a new, long, unique one; move any security codes to a company-owned device or another person; and sign out all other sessions if the service offers that option.

What to remove, not just change

Passwords are only part of it. Also take away:

  • Their own accounts on shared systems, so you can see in the logs that nobody is using them.
  • Their access to files and shared folders, especially anything synced to a personal device.
  • Email forwarding. Check that their mailbox is not quietly forwarding copies of company mail to a personal address, and decide who now reads mail sent to them.
  • Saved logins on company devices, including the browser, before the device is handed to the next person.

Common mistakes

  • Changing only the obvious one. The bank gets changed and the domain account is forgotten.
  • Reusing the old password with a number added. A new password should be unrelated to the old one.
  • Sending the new password in the same chat the old one was shared in. You are rebuilding the problem you are trying to fix.
  • Waiting a week. The risk is highest in the first days, when feelings are strongest and nothing has been changed.
  • No list at all. If you cannot say which accounts the person could open, you cannot be sure you have covered them. That is the problem to fix first.

How to make the next one easy

The pain of a leaver comes from not knowing where the passwords are. The fix is to stop sharing them by hand.

The NCSC says to try to find alternatives to sharing a password at all, for example giving each person their own login. Where sharing cannot be avoided, share only within the smallest possible group of known and trusted people, and consider a password manager. Some let you share more securely, keep a record of who has access, and update everyone when a password changes.

Both the NCSC and the US Cybersecurity and Infrastructure Security Agency (CISA) recommend password managers. CISA’s reason is practical: nobody can remember a unique strong password for every account, so a password manager creates, stores and fills them in. With a team vault, the leaver checklist shrinks to a short list: remove the person, change the shared passwords, done. Our free password generator shows what a strong replacement looks like, and our guide to sharing passwords with staff safely covers the setup in more detail.

Want help setting this up properly?

Doing it once for one leaver is manageable. Doing it for every leaver, with no missed accounts, is easier when the team uses one password manager with shared vaults and a clear record of who can open what. If you want us to roll that out, see our heylogin password management service.

Sources and further reading

  • Password policy: updating your approach, NCSC (UK). Source for changing a shared password when someone is no longer allowed access, an effective movers and leavers process, finding alternatives to sharing, sharing only within the smallest possible group, and password managers for secure sharing.
  • Use Strong Passwords, CISA (US). Source for nobody being able to remember a unique strong password for every account, and password managers creating, storing and filling them in.

Stop impersonation. Control access. Protect your business.

Choose the service you need, or book a security review and we will help you identify the correct starting point.