Alerts & notifications
Email and webhook alerts: drift, failures, restores, clones.
Channels
Alerts post to a webhook (Slack, Mattermost, Discord, or ntfy - format auto-detected, or pick explicitly) and, when SMTP is configured, also email every admin with a branded message. Configure both in Administration > System settings, then use Send test alert / test email to verify.
One email per backup
Change detection happens during backups, so the backup notification and the change details arrive as one message: "Backup complete - changes detected", with a per-object list ([+] added, [-] removed, [~] changed). No-change backups send a plain success message (if subscribed).
Event subscriptions
Email and webhook subscriptions are configured separately: each alert type can go to admin email, to the webhook, to both, or to neither.
| Alert type | Covers |
|---|---|
| Config Backups | changes detected during a config backup (change list included in the message), config backup failures, and the daily overdue-backup watchdog |
| Users & Access Backups | users, memberships, or assignments changed vs the previous Users & Access snapshot (change list included), and Users & Access backup failures |
| Restores | a config or Users & Access restore writes to a live tenant (same-tenant restores) |
| Clones | a clone (config or Users & Access) is applied from one tenant into another. Clones touch hundreds of objects, so instead of a raw change dump the alert leads with the application list, compact per-type applied/failed/ignored counts, and a link to the target tenant's restore history (the link uses the Public URL from System settings when set) |
| Successful backups too | ALSO alert when a backup completes with no changes (noisy; off by default). Applies to whichever backup types are checked above, per channel. |
With the defaults you only hear from IdPVault when something actually changed, failed, was restored, or went overdue.