Signing in and security
Two-step sign-in, passkeys, where you're signed in, new sign-in emails and your team's activity.
Two-step sign-in
Two-step sign-in asks for a code from an authenticator app (like Google Authenticator, 1Password or Authy) after your password, so a stolen password isn't enough. Turn it on under Settings › Security, scan the QR code, and save your backup codes somewhere safe: each one works once if you lose your phone.
Passkeys: sign in with Face ID or Touch ID
A passkey lets you sign in with your fingerprint, face or device PIN instead of typing a password. There's nothing to remember and nothing to leak. Add one under Settings › Security › Passkeys, on each phone or computer you use (or once, if your passkeys sync through iCloud Keychain, Google Password Manager or a password manager). Then choose Sign in with a passkey on the sign-in page. Your password still works too.
Where you're signed in
Settings › Devices lists every browser and phone signed in to your Pingerer account: what it is, roughly where, and when it was last used. Sign out one you don't recognise, or choose Sign out everywhere else to keep only the device you're on.
New sign-in emails
When someone signs in to your account from a browser or phone it hasn't seen before, we email you. If it was you, there's nothing to do. If it wasn't, click Not you? in the email: it signs out every device at once and asks you to choose a new password.
Requiring two-step sign-in for your team
Admins of a team account can turn on Require two-step sign-in on the Team page. Anyone without it is walked through setting it up the next time they open Pingerer, before they can carry on.
Activity: who changed what
Admins can see a team account's activity under Settings › Activity: who added, paused, changed or deleted a site or check, published a status page or posted an update, changed an alert channel, invited someone or changed a role, changed the plan, or made an API token, and when. Search it, or show one kind of change at a time.
API tokens
API tokens are stored scrambled, so not even we can read them back. That's why a new token is shown only once, when you make it: copy it then. You can give a token an expiry date, and each one shows when it was last used. Tokens nobody has used for 90 days are pointed out, with one click to revoke them. See the API page.
Your account's checklist
Settings › Security opens with a short checklist (for example "2 of 4 done"): two-step sign-in on, a passkey added, backup codes saved, and no forgotten tokens lying around. It ticks itself off as you go.
Still stuck? Contact us and a person will reply.