(Many groups have a single email address that is shared between all of its members that need access to the account. Many of the email accounts are shared between multiple people. If they don't, however, I usually resort to sending a disappearing message over Facebook. This is workable but I still don't have any control on how they store it on the other end and they likely aren't storing it securely at all. If they have a GSuite account, I just send a confidential mode email. This means that sending password resets to people isn't always easy. I know a couple associated groups have literal Drive Docs of passwords, with link sharing on, so I want to get rid of those as quickly as possible.Īgain, because of the way our bylaws are set up, not all associated groups have GSuite inboxes. Technical people have been keeping their own KeePass databases and passing those along. There are a couple of challenges I am facing with our current password management structure (there isn't really one):īecause our bylaws limit almost every office to a term limit of one year, we have a ridiculously large amount of turnover and passing passwords on has historically been a challenge to do properly. I imagine roughly 100 people would be using the password manager daily. There are around 200 users in our GSuite and many more are part of some associated organisation. We have many associated groups for which we provide web services, including CPanel hosting and email. I'm the webmaster for a university student union, which is a registered non-profit in Canada.

1password nonprofit pricing