Secure credential handoff

For contractors, clients, IT support, and employee onboarding

Short answer: OncePad is a free, no-account service for sharing a password, secret, or file through an end-to-end encrypted link. The link contains no decryption key, works once, and expires after 24 hours. Files may be up to 25 MB.

The handoff is where credentials escape

A credential may be safe in a vault before and after onboarding yet leak through the Slack message, email, ticket, or shared document used to transfer it. A one-time encrypted handoff removes that durable plaintext copy without requiring the recipient to create an account.

Contractors and clients

Send the OncePad link in the project channel or ticket, then give the passphrase by text or a call. Prefer a scoped, temporary credential, and ask the recipient to move it immediately into their password manager or secrets vault. Revoke it when the engagement ends.

Employee onboarding and IT support

Use separate links for the initial password, recovery codes, VPN configuration, or support token rather than bundling identity, login URL, and credential together. Require a password change at first sign-in and use the service's Erase it now control if the recipient or channel was wrong.

A handoff is not lifecycle management

OncePad does not verify identity, track which employee opened a link, rotate credentials, revoke third-party sessions, or retain an audit trail. Teams that need those controls should use an identity provider, enterprise password manager, or privileged-access system; the one-time link only handles delivery.

A checklist for any handoff

  1. Issue, don't share. Create an account or key for this person, so it can be revoked on its own.
  2. Make it temporary where you can: an initial password that must be changed, a key that expires.
  3. Split the pieces. Username and URL in the ticket; the secret in a one-time link; the passphrase on a call or by text.
  4. Confirm receipt. Ask them to confirm they have it. If they report "not found", someone else may have opened it — erase and reissue.
  5. Plan the end. Note when the access should be revoked, and do it.

What to write

In the ticket or email: "Your staging database login is user contractor-ana at db.staging.example.com. The password is here: oncepad.com/s/7K2QF9XR — it works once. I'll text you the seven-word passphrase." Then text the words. The ticket now documents the handoff without containing anything an attacker can use.

Receiving credentials from a client

The same flow works in reverse, which is often the more useful direction: ask the client to create the link themselves at oncepad.com and send you the link and passphrase separately. They need no account, and you never have to ask them to email a password.

Questions

How should I send login details to a new employee?

Put the username and sign-in address in the onboarding email or ticket, the initial password in a one-time link, and the link's passphrase in a text or call. Require a password change at first sign-in.

Should the username and password be sent together?

No. Splitting them means a single leaked message is never a complete login.

How do I get credentials back when a contractor leaves?

You cannot take back something someone has seen. Revoke the account or key, or change the password, which is why it helps to issue a separate credential to each person.