Most password leaks don’t begin with anyone breaking encryption. They begin with a credential sitting somewhere it was only meant to pass through: an old email, a chat thread, a note in a shared document. Sharing a password securely is mostly about making sure the handover leaves nothing behind.
First, ask whether it needs sharing at all
If the system supports individual accounts, create one and let the other person set their own password. You can remove that account later without disturbing anyone else, and any log the system keeps will show who really did what. Sharing is for the cases where that isn’t possible: a single admin login, a licence key, a router password, a client’s hosting account or a key handed to a developer.
Four questions to ask of any method
- Does a readable copy remain? If the password can still be found by searching the same place next year, it can be found by whoever gets into that place.
- Does it expire? A recipient on holiday shouldn’t mean a credential waiting indefinitely for someone to find it.
- Would you know if the wrong person got it? Most channels can’t tell you whether a message was read, let alone when.
- Can you take it back? Addressing something to the wrong person is an easy mistake. It is much less serious if you can withdraw it.
How the common options compare
| Method | Copy left behind? | Best suited to |
|---|---|---|
| Yes, in mailboxes and usually in backups | Nothing confidential. Here’s why | |
| Chat or text message | Yes, in the history on each device | Short-lived temporary passwords, changed straight after |
| Phone call or in person | No, unless someone writes it down | Short codes, though long passwords get misheard |
| Team password manager | Stored encrypted, by design | Credentials a team keeps using, when everyone is already on it |
| One-time link | No, destroyed when opened or at expiry | One handover, including to someone outside your organisation |
None of these is right for everything. A password manager is the better home for a login your team uses every week; a one-time link suits the moment when you need to get something to someone who isn’t on your system and may never be.
A routine that works
- Set a temporary password if the system allows it, one the recipient will be made to change at first login.
- Create the secret. In Host Dada Secrets you paste the text, up to 50,000 characters, and add a private label so you remember what it was for.
- Choose the shortest expiry that will work. The options are 1 hour, 24 hours, 3 days, 7 days or 30 days. If you know they’re at their desk, an hour is plenty.
- Send the link separately from the context. Tell them which system it’s for in your usual message and let the link carry only the password. You can copy the link, or have it emailed with your name on it so they can tell it’s genuine.
- Warn them it works once. Ask them to have somewhere safe ready, ideally their password manager, before they click to reveal it.
- Check it was collected. Your dashboard shows the time it was opened, and you get an email when it happens. If they say it wasn’t them, treat the password as compromised and change it.
Habits that matter whichever method you use
- Turn on two-factor authentication wherever you can. A leaked password then isn’t enough on its own. Send the setup code by a different route from the password.
- Never reuse the password you’re sharing. Someone who receives it should gain access to one system, not to everything else that shares it.
- Be suspicious of urgent requests. If someone asks for a credential out of the blue, confirm by phone or by a route you already trust. A secure channel doesn’t help if you are sending to the wrong person.
- Change shared passwords when people leave. A shared login has no way of telling a current colleague from a former one.
Passing on several logins at once? See sharing client logins and IT handovers. If you’d like to know what happens to a secret once you’ve pasted it, we set that out in how the encryption works.