Teams & who gets alerted
Ping is built around teams, so the right people get paged — whether that's just you or your whole on-call rotation.
Your personal team and shared teams
- Personal team. Everyone has one. Alerts sent to your personal team reach only you — perfect for your own side projects or a monitor you personally own.
- Shared teams. A team you share with teammates. Alerts sent to a shared team reach everyone on it — the right choice for on-call rotations and anything the whole team should see.
When you create an API key you choose which team it belongs to. That single choice decides who gets alerted by everything sent with that key.
In the app you can switch between the teams you belong to — your personal team and any shared teams — to see each one's inbox:
A shared team lists its members and their roles, so you always know exactly who gets paged:
Adding a teammate is a single invite by email — once they accept and sign in to the app, their device starts receiving the team's alerts automatically:
How your phone is matched to you
When you sign in to the Ping app with your Kunobi email, your device registers to your account automatically — no pairing code, no QR scan. From then on:
- You receive push notifications for the teams you belong to.
- Sign in on more than one device (phone and tablet), and each one gets the alert.
- You can see your registered devices in the Ping tab of your Kunobi profile.
Because alerts follow the team, not a specific phone, on-call handoffs just work. Add someone to the team and their device starts receiving alerts; a new teammate simply installs the app and signs in.
Choosing where to send alerts
| You want to… | Send the key to… |
|---|---|
| Get alerts for a monitor only you own | your personal team |
| Page your whole on-call rotation | a shared team |
| Keep staging and production separate | separate keys (and teams) per environment |
Managing keys
Each API key belongs to one team and carries a non-secret prefix like
ping_live_a1b2c3 so you can recognize it. From the Ping tab you can:
- See each key's team, label, and when it was last used.
- Revoke a key the moment it's no longer needed or may have leaked — alerts sent with a revoked key stop immediately.
- Set an expiry when you create a key so short-lived integrations clean up after themselves.
Revoking a key only stops that key. To move an integration to a different team, create a new key for the new team, update your monitoring tool, then revoke the old one.