BobWork Vault
Team security

How to share passwords securely with your team (and stop pasting them into chat)

To share passwords securely with a team, use an end-to-end encrypted password manager, not chat, email or spreadsheets. Store each login once, share it per item or per folder, give each person the lowest access level they need, turn on two-factor authentication, and remove access the day someone leaves. Rotate any password that was ever sent in plain text.

By the BobWork team · · 5 min read

Add to Chrome — freeCreate a free account

What is the safest way to share passwords securely with a team?

The safest way is a password manager that encrypts each login on your device before it is stored, and lets you share that login with named teammates. Nobody types the password into a message, and nobody keeps a private copy in a notes app.

Good sharing has four properties. The password is encrypted end to end. Access is granted to specific people, not to anyone who has the link or the file. You can choose how much each person can do. And you can take access away in one place.

Chat apps, email and shared spreadsheets fail most of those tests. They were built to move messages and data around, not to control who can use a secret.

Why is sharing passwords in WhatsApp, Slack or email risky?

Messaging apps are designed to keep things forever and copy them everywhere. That is the opposite of what you want for a credential.

  • The message never really goes away. It sits in chat history, in cloud backups, on every phone and laptop the recipient uses, and in any export of the conversation.
  • You lose track of who has it. Messages get forwarded, groups gain new members, and screenshots end up in camera rolls.
  • Offboarding becomes guesswork. When someone leaves, you have no list of which passwords they received, so you cannot know what to change.
  • Search makes it easy to find. Anyone with access to an inbox or chat account can search for "password" and get a tidy list.
  • Account takeover spreads. If one person's email or chat account is compromised, every password ever sent to them is exposed too.

End-to-end encryption in a chat app protects the message in transit. It does not stop the problems above, because the password still lives in plain text at both ends.

What about spreadsheets and shared documents?

A spreadsheet of logins is convenient until it is shared one time too many. Document sharing settings are easy to widen by accident, version history keeps old passwords even after you change them, and anyone who can open the file sees every row.

Password-protecting the file helps a little, but then the file password itself has to be shared, usually in chat. You are back where you started.

If your team runs on a spreadsheet today, treat it as a migration source, not a storage location. Import it into a proper tool, then delete it and empty the trash.

How do the safe options compare?

Here is a generic comparison of common ways teams share credentials. Check each vendor's own documentation for specifics.

MethodEncrypted at restPer-person accessEasy to revokeGood for teams
Chat or emailVaries, readable at both endsNoNoNo
Spreadsheet or shared docVariesWhole file onlyPartlyNo
Browser's built-in password savingYesLimitedLimitedMostly for individuals
Team password manager (zero-knowledge)Yes, end to endYes, per item or folderYes, in one placeYes

For a deeper look at the browser option, see is Chrome's password manager safe for business. To compare team password managers side by side, see our comparison page.

What should you look for in a team password manager?

  • Zero-knowledge encryption. Data is encrypted in your browser or app, and the provider stores only ciphertext.
  • Granular access levels. At minimum, view versus edit. Ideally a level where a teammate can sign in with a login without seeing the password.
  • Folders. Share a whole set, such as all social media accounts, with one action.
  • Clean offboarding. A way to remove a person, reassign what they owned, and list the passwords that should be changed.
  • Audit log. A record of who shared, changed or removed what.
  • Two-factor support. Somewhere to keep authenticator codes so shared accounts can still use 2FA.
  • Import. A way to pull in your existing passwords from a browser or spreadsheet export.

How do you set up secure password sharing step by step?

  1. List the shared accounts. Go through chat history, spreadsheets and browser saves. Note every login more than one person uses.
  2. Pick one tool and one owner. Decide who administers the team vault. Everyone else is invited by that person.
  3. Import existing passwords. Export from your browser or spreadsheet as CSV, import, then securely delete the CSV file.
  4. Create folders by job, not by person. For example: Finance, Marketing, Suppliers, Infrastructure.
  5. Invite teammates and set access levels. Give each person the lowest level that lets them do their job.
  6. Turn on 2FA for shared accounts. Store the authenticator secret in the vault so the team is not dependent on one person's phone.
  7. Rotate anything that was ever sent in chat or email. Generate long, unique replacements.
  8. Set a team rule. "Passwords live in the vault. Never paste them into chat." Pin it where people will see it.

Which access level should each teammate get?

Least privilege is the principle: give people what they need and nothing more. A practical mapping:

  • Owner for the person accountable for the account, such as the finance lead for the banking portal.
  • Edit for people who may need to update the password after a reset.
  • View for people who need to read it, for example to type it on a device without an extension.
  • Login only for contractors, interns or temporary staff who just need to sign in. They can use the account but cannot see or copy the password, which makes offboarding much less painful.

Review access every few months, and always when someone changes role.

What mistakes should you avoid when switching?

  • Leaving the old copies behind. Moving passwords into a vault does not delete them from chat threads, inboxes or the spreadsheet. Clean those up, or at least rotate the passwords they contain.
  • Sharing everything with everyone. It is tempting to make one big folder for the whole team. Split by function so a leaver or a compromised account exposes less.
  • One person holding all the 2FA codes. If the authenticator for a shared account lives only on one phone, the team is locked out when that person is away.
  • No rule for new accounts. Agree that any new shared login is created in the vault first, with a generated password, before anyone signs up.

How does BobWork Vault handle team sharing?

BobWork Vault is a free password manager for teams, and sharing is included in the free plan. Everything is encrypted in your browser with AES-256-GCM, and each item's key is wrapped separately for every teammate it is shared with. The server stores ciphertext only.

You can share a single password or a whole folder, and choose Owner, Edit, View or Login only for each person. With Login only, the Chrome extension fills the login for that teammate but they cannot see or copy it. Invite people from Settings › Team › Invite teammate. When someone leaves, a guided offboarding flow removes their access, hands over what they owned and builds a checklist of passwords to change. Read more on sharing passwords with your team and how the encryption works.

If you are moving from a browser or spreadsheet, the import guide covers CSV from Chrome and other managers. Create a free team vault and move your first shared folder in a few minutes.

Try BobWork Vault — free for your whole team

BobWork Vault is a free, zero-knowledge password manager for teams, made by BobWork (BobOffice, LLC). Shared folders, login-only access, 2FA codes and guided offboarding, end-to-end encrypted. Add it to Chrome or create a free account.

Keep reading

More: free team password manager · free company password manager · company password manager · password management software · how to share passwords with teammates · compare password managers

Questions

Is it safe to send a password over WhatsApp if the chat is end-to-end encrypted?

Encryption protects the message in transit, but the password then sits in plain text in chat history, backups and every device in the conversation. Use a password manager to share it, and change any password already sent in chat.

How do I share a password with someone without them seeing it?

Use a team password manager with a fill-only access level. In BobWork Vault this is called Login only: the browser extension fills the login, but the teammate cannot view or copy the password.

Should every teammate have their own login instead of a shared one?

Yes, when the service supports individual accounts, that is better for accountability. Shared logins are still common for social media, suppliers and legacy tools, and those should live in a shared vault folder.

What should I do with old passwords already sent in chat or email?

Assume they are exposed. Change each one to a new, long, unique password, store it in the vault, and delete the old messages where you can.

Is sharing included in BobWork Vault's free plan?

Yes. BobWork Vault is free and team sharing, shared folders and access levels are included.