# Managing logins for many websites

URL: https://ekom.blog/managing-logins-for-many-websites/
Published: 2023-12-21
Author: Ekom
Topics: How the internet works

> How I keep track of logins, access and two-factor codes across many client websites without sharing passwords or losing control.

When you look after one website, you can remember its logins. When you look after several, each with its own hosting panel, domain registrar, CMS, analytics account and email service, memory stops being a system. It becomes a risk. A couple of months into managing multiple client sites, I found that logins were the part most likely to cause a bad day.

This is the approach I'm using. It's not fancy, and it's still evolving.

## The problems logins cause

- Reused passwords, because remembering fifty different ones is impossible.

- Passwords shared in chat or email, which then live in message history forever.

- One shared account for everyone, so you can't tell who did what and can't remove one person without changing it for all.

- Forgotten two-factor codes, tied to someone's old phone.

- Access that outlives its purpose: an agency, freelancer or employee who left months ago and still has the keys.

- Clients who hold the only copy of a login and can't find it when you need it.

Any of these is survivable. Together, they're how sites get locked out, hacked or lost.

## Principle 1: one password manager, no exceptions

Everything goes in a password manager, with a unique, generated password for each login. I explained why in password managers: the one app I'd install on every device. The manager's master password is the one I memorise, and it's long.

For client work, I keep a separate area, vault or folder for each client. It makes access tidy, and handover is simple: share that folder, not a spreadsheet.

If you work with a team, use a manager that supports shared vaults with permissions. Sending a password in a message is the thing to stop first.

## Principle 2: a named account for every person

Where a platform allows it, each person gets their own login with the lowest permission that does the job. An editor doesn't need to be an administrator. A designer doesn't need access to billing.

The benefits are practical:

- You can see who changed what.

- You can remove one person without disrupting the rest.

- A compromised account has limited reach.

Where a platform only supports one login, such as some basic hosting plans, record who knows it and change it when people leave.

## Principle 3: the client owns the important accounts

The domain registrar, the hosting account and the analytics property should be in the client's name, with me added as a user or manager. If I disappear, the business keeps its assets. If we part ways, there's no argument about who owns the domain. I wrote about this idea for registrars in domain privacy: hiding your details, and it applies just as much to hosting and Google accounts.

That also protects me. I'm not the single point of failure, or the person holding someone else's property.

## Principle 4: two-factor sign-in on everything that matters

Registrars, DNS, hosting, the CMS admin, Google accounts, the password manager itself. Authenticator apps beat text-message codes where there's a choice.

The hard part is the backup. If the phone holding your codes is lost or replaced, you can be locked out of everything at once. Plan for it:

- Save the recovery codes in the password manager (or print and store them safely).

- Know how to move the codes to a new phone: transferring two-factor codes to a new phone walks through it.

- For client accounts where the client has two-factor tied to their phone, agree who approves what.

## Principle 5: an access register

Alongside the manager, I keep a simple register: for each site, which accounts exist, who has access, what level, and when it was last reviewed. It doesn't contain passwords, only the facts. This is part of the system I described in managing several client websites at once: the system I use.

Typical columns: system (host, registrar, CMS, analytics), account owner, who has access, role, two-factor on or off, last review date.

## Principle 6: review and remove

Once a quarter, for each site:

- Go through the user list in the CMS. Remove anyone who no longer needs it.

- Check the people with access to hosting, DNS and analytics.

- Look for accounts with weak or old passwords.

- Check that two-factor is still active.

- Update the register.

When a contractor finishes, the aim is to remove their access the same day. It's far easier to do it at the end of a job than to remember months later.

## Principle 7: agree how to share when you must

Sometimes a client sends credentials the wrong way, in an email or on a messaging app. Don't scold. Move them into the manager, change the password if it matters, and gently explain a better approach. A short "how we handle access" note at the start of a project saves awkwardness later.

## What I avoid

- Spreadsheets of passwords.

- Browser-saved passwords on a shared computer.

- Using my personal logins for client systems.

- Giving administrator access by default.

- Leaving a default "admin" username in place.

## Starting from a mess

If you inherit a pile of unknown logins, don't try to fix everything at once. Start with the three accounts that can take a business offline: the domain registrar, DNS and hosting. Secure those first, with strong passwords and two-factor. Then work outwards.

## Key takeaways

- Use one password manager with separate spaces per client.

- Give each person a named account with the least access they need.

- Keep the client as owner of domain, hosting and analytics.

- Switch on two-factor, and plan for lost phones.

- Keep an access register and review it every quarter.

## Related reading

- How to create passwords you can remember

- Password managers: the one app I would install on every device

- Brute-force attacks on login pages

Which three accounts could take your business offline tomorrow? Check who has access to them.

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
