How should clients' passwords be managed? By "clients" of course I mean people who you provide a service to, people who need you to work on their stuff (their websites, their servers, their emails, or other services they use in general).
Every time I read about password managers, I always see examples and arguments that only involve personal passwords, not passwords managed on behalf of other people. And I'm not sure if using a password manager for this purpose is a good idea, or if there are better standard practices. What if I'm managing passwords for a hundred clients, and I get hacked? Should I tell each client "Sorry, I got hacked, now we need to change your email password?" A better option would be to avoid storing other people's passwords, but that would mean you'd have to keep asking the client to provide their password every time you need to access their services (which might be often or rarely, depending on the kind of support). Lots of clients might not even know (or regularly forget or lose) some of their passwords, for example those needed to manage their domains, or their web panels, etc., all stuff they never touch but it's still technically "their stuff" anyway.
So I'm wondering if there are some better methods, policies, or practices to deal with these scenarios, or if the usual password manager with "all eggs in one basket" (my eggs and everybody's eggs) is still the only solution.