The first question is not which password manager has the longest feature list. It is which accounts matter, who owns them and how the business would recover if its usual administrator were unavailable. Email, domain, accounting and primary cloud accounts often control recovery for many other services.
Prefer identities and delegation over sharing
Give people their own supported accounts and appropriate roles. A common administrator password makes it hard to revoke one person’s access or understand an action. Where a provider supports delegation, use that instead of sending a login to a supplier. Keep the legal/customer owner in control of primary accounts and renewal/recovery contacts.
A reputable supported business password manager can help maintain unique credentials and controlled sharing where sharing is genuinely necessary. Check organisation ownership, access review, MFA, export/recovery and the process when someone leaves. Do not treat a personal vault controlled by one departing employee as the business’s only asset register.
Choose strong authentication and usable recovery
Use MFA and passkeys where suitable and supported, with secure account/session settings. Understand the actual provider’s recovery process; enabling a second factor does not mean recovery is safe. Keep recovery codes or approved alternatives protected separately from the ordinary login, limit access and record when they are replaced or used. Do not paste them into tickets, public forms, source files or an AI conversation.
Avoid circular recovery: if the domain email fails, the registrar and email administrator should not both depend solely on that same inbox. The business needs an authorised route which survives a lost device or absent administrator. Recovery controls must not quietly become a weaker back door that bypasses the strong login.
Make joining, leaving and supplier access routine
Record which systems a role can use and approve access for a purpose and duration. Remove unnecessary permissions, revoke sessions/tokens where supported and rotate shared secrets after exposure or a relevant departure. A directory account being disabled may not revoke every third-party session or API token automatically; verify the actual system behaviour.
For a supplier, agree scope, access method and exit before the session. Do not ask for a customer’s full password collection to diagnose one issue. Use minimised temporary access and preserve confidentiality. Document exceptions where a legacy provider cannot support the preferred controls, and decide whether that risk is supportable rather than misreporting it as secure.
Finally, practise an appropriate recovery scenario without exposing real secrets or disabling safeguards. The useful evidence is that authorised people can recover and unauthorised people cannot, within the actual supported provider process—not merely that a settings screen displays “MFA enabled”.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027