A modern business runs on a dozen online accounts. They are usually opened in a hurry, by whoever was available at the time: a freelancer, an agency, a co-founder who has since left. Years later the company pays for them but does not control them. The fix is simple, and it is much easier before something goes wrong.
Make an inventory
Write down every account, who can log in and which email address it is registered to. A typical list:
- domain registrar and DNS;
- hosting, servers and backups;
- business email and the website’s sending services;
- the code repository of the website or product;
- analytics, search console and tag manager;
- advertising accounts;
- payment provider and bank connections;
- social media pages and business profiles;
- software subscriptions such as CRM, invoicing and help desk.
What “in the company’s name” means
For each account, three things should be true. The legal holder is the company. The main login uses an email address at the company’s domain rather than a personal or contractor mailbox. At least two people inside the company can recover access, with two-factor authentication kept on company devices or in a shared password manager.
Contractors and agencies should get their own user access, which you can remove at any time, rather than being the owner.
Moving an account that is not yours
Most services allow a change of ownership: domains through a registrar transfer or a change of registrant, analytics and advertising accounts by adding you as an administrator and then removing the previous owner. Ask for it in writing, keep the confirmation emails, and check afterwards that the previous holder no longer has admin rights. Start with the domain, because email and the website both depend on it.
Keep it current
Review the list when someone leaves, when you change supplier and at least once a year. It takes an hour and protects the assets the whole business stands on.
Opening these accounts correctly from day one is part of how we deliver websites and launch infrastructure. For email in particular, see SPF, DKIM and DMARC.