How to Share Passwords Securely: Best Practices
Why sending passwords over WhatsApp, email or Slack is risky, and safer options: shared vaults, one-time secret links and renewing passwords after sharing.
Sooner or later everyone has to share a password: a family member wants the streaming login, a freelance developer needs FTP access, a new colleague has to get into the CRM. Sharing is sometimes unavoidable; the real question is how you do it. This guide explains why pasting a password into a chat is a bad idea and which safer methods to use instead.
Why Is Password Sharing Risky?
A password is strong only while it stays secret. Once you share it, more than that one message leaves your control:
- Chat history stays on devices and in backups for years.
- The recipient can take a screenshot, write it down or forward it without thinking.
- There is no way to take it back; deleting your message does not delete their copy.
- If the account is compromised, it becomes almost impossible to tell where the secret leaked.
A 20-character password with symbols is not worth much if it has been sitting in a chat history for three years. Security is about the password's life cycle as much as the password itself.
Common but Dangerous Methods
| Method | Main risk |
|---|---|
| Passes through several servers; stays in Sent and in the recipient's inbox indefinitely; easy to forward to the wrong person. | |
| End-to-end encrypted in transit, but history stays on the phone, linked devices and backups, and moves with a new phone. | |
| Slack / Teams | Workspace history is searchable and, depending on plan and settings, can be exported by admins. |
| "passwords.xlsx" on the desktop | No access log, copied to several devices by cloud sync, a first target for ransomware. |
None of these offer one-time reading, access logs or revocation. Once written, the password stays there, and the recipient's device decides for how long.
The Golden Rule: Least Privilege
Everyone gets only the information they need, for only as long as they need it:
- Give it only to those who need it. "The whole team might need it" makes the exposure needlessly large.
- Share access, not the secret. Where possible, use the service's own invitation or profile features: adding a member to a subscription or inviting a user is always safer.
- Think short-term. For a temporary need, plan from the start to change the password when the job is done.
- Never share your personal account. Admin accounts are personal; everyone signs in with their own identity and gets permissions through roles.
Controlled Sharing With a Password Manager
The professional solution is a password manager's shared vault (or collection):
- The password is synced end-to-end encrypted to the recipient's device; no copy lands in a chat history.
- In most products the recipient can autofill without seeing the password, and some let you disable viewing entirely.
- Access can be revoked instantly, and a changed password syncs to everyone automatically.
- Business plans log who accessed which entry and when.
Common managers such as Bitwarden, 1Password and Proton Pass offer shared vaults in their family and team plans. With KeePass-style tools a shared database file is used, so the file itself must travel over a secure channel.
What Are Self-Destructing Secret Links?
When you need something quick, one-time secret link tools are the answer:
- You type the password into the tool; it is stored encrypted and you get a single-use link.
- You send the link through chat.
- The recipient opens it and sees the password once; it is then deleted from the server. A second visit finds nothing.
The password never enters the chat history; only a dead link remains there.
Three rules for using them well
- Split the channel. Send the link by chat and any extra unlock password through another channel, such as a phone call.
- Choose a short expiry. The link should expire on its own even if it is never opened.
- Match the sensitivity. These tools suit moderately sensitive, temporary sharing. The recipient can still take a screenshot; no tool can prevent that. For admin and root credentials, use a password manager.
Shared Accounts in Organisations
First ask: does this account really have to be shared? Most modern services support individual users and role-based access (SSO, RBAC), which is always better because you can answer "who did what".
If a shared account is unavoidable (legacy systems with a single login, social media accounts and so on):
- The password lives in a shared vault, never in anyone's personal vault or browser.
- The account has an owner who is responsible for the access list.
- The password is changed whenever someone leaves the team or company.
- Two-step verification is enabled, and the recovery codes are kept in the same vault.
NIST SP 800-63B does not recommend arbitrary periodic changes for individual accounts. Shared and service accounts are different: event-driven changes (someone leaves, something looks suspicious) are the right practice there.
After Sharing: The Password's Life Cycle
| Situation | What to do |
|---|---|
| Temporary need is over | Change the password, update the vault |
| A team member left | Change the shared password, remove access |
| Suspicious session or report | Change the password now, sign out all sessions |
| Password appears in a breach list | Change it; check other accounts that used it |
If you let someone else see a password, assume it is no longer only yours and renew it when the job is done. The new one should be long and randomly generated; as NIST stresses, length matters more than complex character rules.
Frequently Asked Questions
Isn't WhatsApp end-to-end encrypted? Why is it risky? In transit, yes. The risk is after delivery: the message stays in chat history, backups and linked devices, and a screenshot can be taken at any time.
I need to share a password right now. What is the fastest safe way? Use a one-time secret link; send the link by chat and any unlock password through another channel. Change the password when the job is done.
How do I share subscription accounts with my family? Use the service's own profiles or extra-member feature if it has one. If you must share a password, a family plan password manager's shared vault is the cleanest solution.
Can I take back a password I shared? No. A password that has been seen cannot be unseen; the only option is to change it. Plan every share as temporary.
Are password managers safe? Reputable managers use a zero-knowledge model: your vault is encrypted on your device with your master password and is not readable on the server. The critical point is your master password: make it long and unique, and enable two-step verification.
Done Sharing? Time for a New Password
Every password you renew after sharing should be strong and random. The Password Generator creates it in your browser with cryptographically secure randomness (crypto.getRandomValues); it is never sent or stored. Measure its strength with the Password Strength Test and see whether an old password appears in breach lists with the breach checker.
Generate Strong Credentials Instantly
Hardware-backed Web Crypto API with zero logging and zero server contact.