Notification Reference Table
Every notification BYOVault can send, in one table: what triggers it, how often it checks, who receives it, and whether an operator can turn it off. See the individual pages for the full behavior behind each row.
| Notification | Cadence | Recipient | Can Be Disabled? |
|---|---|---|---|
| Connection health | Checked every 15 minutes. M365 consent and storage reachability are only re-verified once an hour. Resent on every 15-minute cycle for as long as a problem persists. | The tenant’s own Client Alert Recipients. | No dedicated toggle. Leaving Client Alert Recipients empty means the check sends nothing at all — there is no operator fallback for this alert. |
| File-server agent has stopped checking in | Checked hourly, globally across every tenant. Flags an active agent once it has gone quiet for more than 30 minutes. | The affected tenant’s Client Alert Recipients. If that tenant has none configured, the alert falls back to the operator’s own account-level recipients (or account login email, if the operator has not configured any either) so it never silently reaches no one. | No dedicated toggle. Because of the operator fallback, this is the one alert in this table that cannot be fully silenced by leaving recipients unconfigured. |
| 24 hours’ advance warning (backup, archiving, retention lock) | Checked hourly. Each of the three concerns is tracked independently and sends once per distinct occurrence, not once per hourly check. | The tenant’s own Client Alert Recipients. | No dedicated toggle. Leaving Client Alert Recipients empty means the check sends nothing at all. |
| Self-service request lifecycle (submitted, approved, rejected, completed, failed) | Sent immediately at each stage transition — not on a recurring check. | The requesting end user, always. The tenant’s own configured IT contacts are copied on every stage, not only on submission. | The requester’s own copy cannot be turned off. The IT-contact copy is configured separately, on the Self-Service tab’s own recipient list — leaving that list empty means only the requester is notified. |
| Operator digest | Daily, weekly, or monthly, per the operator’s own configured day, hour, and time zone. | The operator’s own configured recipient list, or their account login email if none is set. | Yes — disabled by default, and each operator turns it on or off independently for their own account. |
Client-facing vs. operator-facing
The first four rows all reach a client’s own registered contacts, configured per tenant.
The operator digest is entirely separate — scoped to the operator’s own account, covering their own backup, job, tenant, account, and restore activity across every tenant they manage. See Operator Notifications & Digests for the full detail.
The operator digest is entirely separate — scoped to the operator’s own account, covering their own backup, job, tenant, account, and restore activity across every tenant they manage. See Operator Notifications & Digests for the full detail.
No per-category opt-out for client-facing alerts
Connection health, the stale-agent alert, and the 24-hour advance warning share one Client Alert Recipients list per tenant — there is no way to receive one of the three without the others.
The only available control is the recipient list itself, set on Client Alert Recipients.
The only available control is the recipient list itself, set on Client Alert Recipients.