Skip to content
SafeHanded Docs

Notifications

SafeHanded can tell your team when things happen — most importantly, the instant a subject submits a credential so you can reveal it while they’re still on the line. Email notifications are on every plan; Microsoft Teams and Slack channels are on Team and above.

Channels

Section titled “Channels”
  • Email — built in, branded per client, with a plain-text alternative and no tracking pixels.
  • Microsoft Teams — a card in a channel, through a Teams workflow.
  • Slack — a message in a channel, through a Slack app’s incoming webhook.

Notifications never contain the credential, the request link or the challenge code. Chat messages carry the event, the subject, the ticket reference and who requested it, with an Open in SafeHanded button. Anyone in the channel can read them, so pick a channel for your IT team.

Connect Microsoft Teams

Section titled “Connect Microsoft Teams”
  1. In Teams, open the channel’s ⋯ menu → Workflows, and choose Send webhook alerts to a channel (in some tenants it’s called Post to a channel when a webhook request is received).
  2. Confirm the team and channel, add the workflow, and copy the URL it gives you.
  3. In SafeHanded, go to Settings → Integrations → Connect, choose Microsoft Teams and paste the URL.
  4. Choose the events (below) and press Test connection: a “SafeHanded is connected” card appears in the channel.

Teams runs the workflow in Power Automate, which sometimes queues it: a card can take a few minutes to appear. If one never arrives, check the workflow’s Run history in Teams (Workflows app): a run that failed there isn’t reported back to SafeHanded.

Connect Slack

Section titled “Connect Slack”
  1. At api.slack.com/apps, choose Create New App → From scratch and pick your workspace.
  2. Open Incoming Webhooks, turn it on, choose Add New Webhook to Workspace, pick the channel and copy the URL.
  3. In SafeHanded, go to Settings → Integrations → Connect, choose Slack and paste the URL.
  4. Choose the events and press Test connection.

Treat the webhook URL like a password: anyone who has it can post to the channel. SafeHanded stores it encrypted and never shows it again.

What a channel can be told

Section titled “What a channel can be told”
EventWhen
Credential submittedThe subject submitted the credential: reveal it while they’re still on the line.
Credential revealedA recipient opened it. Off by default, because it’s frequent.
Credential destroyedIt was purged, for example when the linked ticket closed.
Request reportedThe person who opened the link reported it as unexpected; the link is revoked.
An integration is failingAnother connection (ticketing, SIEM, mailbox…) stopped working. Never posted through the failing channel itself.
Organisation recovery key usedSomeone opened a credential with the organisation recovery key.
Member disabled with stranded requestsA disabled member left requests that need re-issuing.

Requesters also get their own events (submitted, expired, locked, reported) by email and in the app, and Owners and Admins are told about recovery-key use and failing integrations by email, whether or not a channel is connected.

Choosing your emails

Section titled “Choosing your emails”

Each person chooses their own emails under Your profile → Email notifications. You can turn off:

  • Credential submitted
  • Expired links and resend requests
  • Credentials destroyed and tickets reopened
  • Shared secret viewed
  • Integration failing or recovered (Owners and Admins)

To send your notifications to a different address, such as a shared helpdesk mailbox, choose Change next to Send notifications to and enter the code we email to the new address. Nothing changes until the code is entered, and your sign-in address is told about the change. Sign-in links and alerts about your account always go to your sign-in address.

Everything still appears under the bell in the app. Security alerts always arrive by email: a reported request, a locked verification or share, a request that needs a new link, and organisation recovery key use or changes.

Section titled “Related”