The safest way to send a password to a client is through a one-time link that expires and stops working after it’s been read, with the username or context sent separately. Don’t put passwords in email, text messages or shared documents, where they stay searchable long after they’re needed.
If it’s a temporary password, ask the client to change it on first login. That one habit limits the damage if anything goes wrong in transit.
Why email and text are the wrong place for passwords
A password sent by email doesn’t disappear when the client reads it. It sits in your sent folder, their inbox, any device that syncs either account, and every backup. Anyone who later gets into either mailbox can search for “password” and find it.
The IRS warns tax professionals about exactly this. Its Publication 4557, Safeguarding Taxpayer Data describes thieves tricking people into disclosing usernames and passwords, and recommends protecting email accounts with strong passwords and two-factor authentication. Text messages carry the same problem: they persist on phones and in cloud backups.
Step by step: sending a password securely
- Generate a strong temporary password. CISA’s guidance on strong passwords is to make them long (at least 16 characters), random and unique, and to use a password manager. A temporary password should meet the same bar.
- Put the password in a one-time link. Use a tool built for secrets, where the link expires and can burn after it’s read.
- Add a PIN, sent another way. If you email the link, give the PIN by phone. Someone who intercepts one channel won’t have both.
- Send the username or context separately. “Your portal login is your email address; the password is in the secure link I just sent” keeps the two halves apart.
- Watch for it to be opened. If the link hasn’t been opened when you expected, check with the client before resending.
- Ask them to change it on first login. Then the password you sent stops mattering.
- Don’t keep a copy. Once it’s delivered, don’t save the password in a note, a ticket or the client’s file.
What not to do
- Don’t send the username and password in the same message. Together they’re a complete login for anyone who sees them.
- Don’t put passwords in an intake form. Form answers are stored and reviewed as information. A credential needs expiry and a record of when it was opened, which a form field can’t give you.
- Don’t paste passwords into a file’s comment thread. Discussion about a document belongs with the document; secrets don’t.
- Don’t upload a text file with credentials. It becomes a stored document with a password in it.
- Don’t reuse a “standard” temporary password. If every client gets the same one, one leak exposes them all.
A message template you can copy
Hi [Name], I’ve sent your temporary password through a secure link that will expire in 24 hours and can only be viewed once. I’ll call you with the PIN to open it. Your username is your email address. Please change the password the first time you sign in. If the link has expired before you get to it, just let me know and I’ll send a new one.
When the client needs to send you a password
The same rules apply in reverse. If a client needs to give you access to a payroll system, a domain registrar or a bank portal, they shouldn’t email it either. Send them a secure way to do it, and once you’re done, ask them to change the password or remove your access.
Better still, where the system allows it, ask the client to add you as a separate user. Shared logins are hard to track and hard to revoke.
How this works with Secure Drop
MyDocUploads Secure Drop is built for things that aren’t files: credentials, one-time links and sensitive notes. You write the password or code, optionally attach a small file, set an expiry of 24 hours, 7 days, 30 days or never, and add an optional password or PIN. The recipient opens it by a one-time link with no account needed. You can see when it was viewed, from where, and it can burn after the first read. Every send is logged in the client’s workspace, so the record sits with the rest of their work.
It sits alongside the other parts of MyDocUploads rather than replacing them. Use Conversations to discuss a file, a file request in Core to collect documents, and Secure Drop only for the secret itself.
A quick checklist
- Strong, unique temporary password generated?
- Sent by a one-time link that expires, not by email or text?
- PIN or username sent by a different channel?
- Opened confirmation checked?
- Client asked to change it on first login?
- No copy kept in notes, tickets or files?
If you’d like to send your next password this way, you can start a 14-day trial of MyDocUploads.
This article is general information, not legal, tax or professional advice for your specific situation.
Frequently asked questions
Is it safe to email a password if I delete it afterwards?
Not really. Deleting it from your sent folder doesn’t remove it from the client’s inbox, synced devices or backups. A one-time link that expires avoids leaving a copy behind.
Should I send the username and password together?
No. Send them by different channels, such as the password by secure link and the username or PIN by phone, so one intercepted message isn’t a complete login.
Does the client need an account to open a Secure Drop?
No. Recipients open a Secure Drop through a one-time secure link with no account or sign-up.
How strong should a temporary password be?
CISA recommends passwords that are long (at least 16 characters), random and unique, managed with a password manager. Ask the client to change a temporary password on first login.