Completing & purging
A credential shouldn’t outlive the job. SafeHanded destroys it in three ways, whichever comes first. Purging deletes the envelope; there’s nothing left to decrypt.
1. Manually
Section titled “1. Manually”Click Complete and destroy on the request. The envelope is deleted, the status becomes
Completed, and the audit log records a purged event with reason manual. A note is posted to the
linked ticket. If your policy turns on rotation reminders, you’re also reminded to ask
the subject to change the credential (by a deadline, if one is set), and the ticket note says so.
2. By time (TTL)
Section titled “2. By time (TTL)”When a request’s time-to-live passes, SafeHanded purges it automatically with reason ttl. Unopened links are separately expired when their open window passes. You set the allowed lifetimes in policy.
3. When the ticket closes
Section titled “3. When the ticket closes”This is the one that means you never have to remember. When the linked ticket reaches the configured status, SafeHanded purges the credential automatically:
- You close the ticket in your helpdesk as normal — no action in SafeHanded.
- SafeHanded picks it up on its next status poll of your helpdesk.
- If the trigger status is met: a submitted request is purged (reason ticket_closed); an unsubmitted request is revoked (an admin can turn this off). An optional grace period lets a quick reopen cancel the purge.
- A final private note is posted — “the credential for Jane Doe was destroyed because this ticket was closed at 16:42 on 6 Oct 2026 by Sam Patel” — and you’re notified. If your org enabled it, the chain-of-custody certificate PDF is attached to the ticket as evidence.
The default trigger is resolved or closed; an admin can change it. See how ticketing works.
If a ticket is reopened
Section titled “If a ticket is reopened”Nothing is restored — the credential is already gone. You’re notified, and the request page explains what happened with a Request again link to start a new request.