Skip to content
SafeHanded Docs

The handoff page explained

When you request a credential, your user opens a handoff page — the branded page where they type the password. This explains what they see and why it’s safe. It’s written so you can point your own users to it (or lift the wording into your own comms).

What your users see

Section titled “What your users see”
  • Your branding — your (or your client’s) logo, name, colours and support contacts, so the page is obviously from their IT team.
  • Who’s asking — the requester’s name and role, the ticket reference, and the subject’s own name.
  • When it expires — when the link closes; the link is single-use and short-lived.
  • A “verify this request” panel — real contact details, and (where set) the requester’s photo and phone extension, so the user can recognise and reach a real person before typing anything.

Why it’s safe to use

Section titled “Why it’s safe to use”
  • The password is encrypted on their own device before it’s sent. Nobody at SafeHanded, and no server, can read it.
  • It’s destroyed when the technician finishes or the ticket closes.
  • The page has no navigation, no marketing and no third-party scripts — one job, and it works on a phone.

What to tell your users

Section titled “What to tell your users”

Two things keep them safe, and they’re worth putting in your onboarding material:

  1. Only ever type your password on the address you expect — safehanded.com, or your IT team’s own address if they’ve set one up (e.g. secure.yourcompany.com).
  2. If you’re unsure a link is genuine, check it first. Anyone can paste a link into the link checker before opening it, to confirm it’s a real SafeHanded link and who issued it.
Section titled “Related”