The need-to-know basis is good, but defeats the purpose of having the shared database. If we could tier access, and grant permissions, then that might be a mor

The need-to-know basis is good, but defeats the purpose of having the shared database. If we could tier access, and grant permissions, then that might be a more viable option. I'll look into it. We can change our own passwords when an employee leaves, but that leaves all of the client passwords. If we set up their (for example) hosting account and solely managed it, changing the password would be fine. However, we have a large number of clients who co-manage stuff with us -- we both access their hosting, domain registrar, mailchimp/constant contact, advertising, etc accounts. We can't really go through and change a few hundred client passwords or email them urging them to change passwords so that one of our employees doesn't screw with them.