Practical guideBy Torsten Schubert, Monswyk AG · Last updated: July 2026
Sooner or later everyone needs to hand a password to someone else: the streaming login for the family, the router password for a guest, the agency account for a colleague. Most people use the worst possible channel for it.
A password sent in chat or email is stored in plain text, forever, on devices and servers you do not control — and you can never take it back.
This guide compares the methods that actually work, from shared password-manager vaults to one-time links and WiFi QR codes — and shows how to cleanly revoke access when someone leaves.
The alternativesThere is no single answer — the right method depends on who needs access and for how long:
|
| Shared vault in a password manager (e.g. 1Password Families, Bitwarden Organizations, a shared KeePass file) | Families and teams with ongoing shared access | Yes — remove the member | Password changes sync to everyone automatically; access is logged |
| One-time secret link (self-destructing note) | A single handover to someone outside your tools | Partially — the link expires | The recipient must store the password properly on arrival |
| WiFi QR code | Guests on your network | Yes — change the WiFi password | Guests connect without ever seeing or storing the password as text |
| Email, chat, spreadsheets | — | No | Searchable forever, no control, no audit trail |
Create a WiFi QR code for guests (free, runs locally)