How to share client logins and run an IT handover

Agencies, freelancers and IT teams pass on credentials constantly: a hosting login for a new client, a WordPress admin account at the end of a project, an API key for a contractor, recovery codes when someone changes role. These handovers are routine, which is exactly why they tend to end up in an email thread that nobody ever cleans up.

Start with a list, not a message

Before sending anything, write down what’s being handed over: each system, the login address, what level of access it gives and who’s receiving it. You’ll spot accounts nobody remembered, and you’ll end up with a document that can safely live in the project folder, as long as the passwords themselves aren’t in it.

A routine for each credential

  1. Prefer a new account over a shared one. If the system allows individual users, create one for the recipient and hand over the invitation. Only share an existing login when there’s no other option.
  2. Create one link per credential, per person. Separate links mean separate timestamps, and one failed handover doesn’t affect the rest.
  3. Label it for your records. Something like “cPanel login for Acme Ltd”. The recipient never sees the label. It appears on your dashboard and in the email telling you the link was opened. It isn’t encrypted, so keep the password itself out of it.
  4. Pick a realistic expiry. Choose from 1 hour, 24 hours, 3 days, 7 days or 30 days. The default is 24 hours. For a planned handover call, use the shortest. For a client who’ll get to it at some point this week, 7 days is more honest than a link that dies before they read it.
  5. Send the context separately. Put the login address and username in your usual message, and only the password in the link.
  6. Follow up on what was opened. You’ll get an email for each one, and your dashboard shows anything still waiting. Revoke unopened links once they’re no longer needed.
  7. Have the password changed. The handover ends when the recipient sets a password you don’t know, and turns on two-factor authentication if it isn’t already on.

Wording you can use

Clients who haven’t seen a one-time link before may need a sentence of explanation:

I’m sending the login for your hosting account as a one-time link, so it doesn’t sit in our email. The login address is [address] and your username is [username]. The link only works once and expires on [date]. Please have your password manager or somewhere safe ready before you press Reveal, as you won’t be able to view it again. Once you’re in, please change the password. If the page says it’s already been opened and that wasn’t you, let me know straight away.

Common situations

Taking on a new client

You’ll often need access to their domain, hosting or website. Rather than having them email it, ask for a user account of your own where the system supports that. Where it doesn’t, ask them to send a one-time link. It’s free, but they’ll need to create an account and confirm their email address first, since only signed-in users can create a secret.

Handing a finished project over

Send each admin login separately, confirm that each one has been collected, and ask the client to change the passwords. Then delete or disable your own access, and tell them you’ve done so. Leaving a former supplier’s account active is a common loose end.

A new starter or a contractor

Individual accounts first. For anything that has to be shared, such as a licence key or a device password, use a link with a short expiry timed for their first morning. When a contractor finishes, change whatever they were given, because a shared password can’t be un-shared.

API keys, certificates and recovery codes

Text secrets take up to 50,000 characters, which is plenty for keys and lists of recovery codes. Key and certificate files can also be sent as files. Where possible, issue a key for one person and one purpose, so that revoking it later doesn’t break anything else.

When to move beyond one-time links

A one-time link is for getting a credential from one person to another. If your team uses the same logins every week, a team password manager is a better long-term home, with the link as the way credentials reach people outside it. And for why this all matters, it’s worth reading why you shouldn’t email passwords and how to share a password securely.

Common questions

How do I ask a client to send me their login securely?
Ask them to create a free account and send you a one-time link. There’s no way to send them a request form, so they do need to sign up and confirm their email first. If they’d rather not, a temporary password read out over the phone and changed afterwards is a reasonable fallback.
Can I prove when a login was handed over?
Your dashboard records when each link was created and opened, and keeps that for 90 days after the link’s expiry. It records that the link was opened and when, not who opened it. If you need the record for longer, copy the times into your own handover notes.
Should a client’s login go in our project management tool?
Not as plain text. Those tools are searchable, widely shared and usually kept for years, so a password in a task behaves just like a password in an email. Put the fact that it was handed over in the task, and leave the password out.
Is a one-time link enough for a full handover?
It deals with moving the credentials, which is only part of it. The handover isn’t finished until the receiving party has changed the passwords, and access for people who no longer need it has been removed.

Send your next secret as a one-time link

Free to use. Create an account and confirm your email address, then the link is yours to send. Whoever receives it doesn’t need an account.

Create a secret

More guides

All guides

Host Dada Secrets is one of the tools from Host Dada. Read more on the Host Dada one-time secret tool page.