Everyday use
This section covers what a technician does day to day. If you’ve done the quickstart, you’ve already seen the core loop.
The two directions
Section titled “The two directions”- Request a credential (inbound). Ask a user to hand you a password or key. It’s encrypted to you in their browser, you reveal it after a passkey touch, and it’s destroyed when you’re done. → Sending a request
- Send a secret (outbound). Send a credential, note or file to someone as a one-time link — the Password Pusher / Bitwarden Send use case, with the same audit trail and ticket lifecycle. → Send a secret
The request lifecycle
Section titled “The request lifecycle”A request moves through: pending → opened → submitted → completed, and can also become expired or revoked. You can issue a new link, revoke a live link, allow a resubmission, complete and destroy a submitted credential, or revive an expired request.
In this section
Section titled “In this section”- Sending a request — subject, template, justification, ticket, TTL, recipients, verification, delivery.
- Verifying the subject — a spoken code, an emailed or texted one-time code, either, or both.
- Revealing a credential — the passkey step-up, hold-to-peek, auto-clear.
- Completing & purging — manual, by time, or by ticket close.
- Send a secret — outbound shares with expiry, view limits and QR codes.
- Encrypted attachments — sending files safely in either direction.
- Request presets & templates — save common request setups.
- Request from a ticket — create a request without opening SafeHanded.