Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My whole team shares the same passwords and I know it is a risk

Short answer

Shared logins mean you cannot tell who did what, cannot remove one person without changing the password for everyone, and the password usually sits in chat or a spreadsheet. A company password manager with named users, strong unique passwords and two-step verification fixes most of it. Move the most important accounts first and change each password as you do.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Passwords live in a WhatsApp group, an email thread or a spreadsheet.
  • Several people use the same login for one system.
  • When someone leaves, nobody is sure which passwords they knew.
  • The same password is used on more than one account.
  • Something was changed in a system and nobody can say who did it.

Why does this happen?

  1. Sharing is the quickest way to get started

    A new tool arrives with one login, and the founder passes it on. Years later that is how the business still works, and nobody owns the clean-up.

  2. Reused passwords turn one leak into many

    The NCSC says each important account needs its own strong password, and that reused passwords on business-critical accounts should be changed as soon as possible. A shared password reused elsewhere puts every account that uses it at risk.

  3. Password managers solve the memory problem

    The NCSC lists the benefits: a unique password for each account without memorising them, automatic strong passwords, autofill that only works on the correct website, which helps against phishing, and sync across devices. It also says the manager's primary password is the key and that the manager itself should be protected with two-step verification.

  4. Passkeys remove the password where they exist

    The NCSC recommends passkeys as the first choice wherever they are offered, and a strong unique password with 2-step verification for other accounts.

  5. Shared logins hide who did what

    With one login for five people, an audit trail names nobody. Many services offer separate named users or roles. If the service does, a separate login for each person is better than a shared one.

What can I do about it today?

  1. List the shared accountsWrite down every system the team logs in to, and which ones share a login. Start with email, banking, payments, the website host and app stores.
  2. Pick one company password managerChoose a business plan with named users, not personal accounts. Ask your IT provider if you have one.
  3. Protect the manager with two-step verificationThe NCSC says to protect the manager account itself, so that learning one password is not enough.
  4. Create separate users where the service allows itMost business tools let you add team members with roles. Use that instead of a shared login.
  5. Change a password when you move itAnything that has been in a chat or a spreadsheet should be treated as known. Set a new one and delete the old message.
  6. Do not move everything in one weekendSwitching all accounts at once breaks things. Start with the most important, one at a time.

When should I bring someone in?

  • A system has only one login and cannot add users, such as an old app or a hosted account.
  • Servers or developer tools are shared, not just websites.
  • You suspect a shared password has already been misused.

How do I handle it?

  1. Map who needs whatA one-page table of systems, owners and who needs access, so each person has only what their work needs.
  2. Move accounts in order of damageEmail and money first, then the website and store accounts, then the rest.
  3. Replace shared logins with named accessFor servers, code repositories and cloud accounts, each person gets their own access that can be removed alone.
  4. Rotate secrets that were exposedPasswords, API keys and tokens that appeared in chat or code are replaced, and the old ones are switched off.
  5. Write the rules on one pageHow to add a person, how to remove one and what to do if a password leaks.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is a shared password ever acceptable?

When a service gives you no way to add users, a shared login kept in a company password manager is better than one passed around in chat. A separate login for each person is better still.

Is a spreadsheet of passwords safe?

The NCSC advises that anyone with access to a written record could copy the passwords, so you must limit who has access. A password manager is designed for this.

What if the password manager company is hacked?

Protect the manager with a strong primary password and two-step verification, as the NCSC advises, and keep your own recovery plan.

Do I need to tell the team why?

Yes. A short explanation of what happens when one person leaves makes it much easier to adopt.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.