ALT · Alerts & Notifications
Email notification preferences
Choose what lands in your inbox, and when things count as expiring.
3 min read
Two different screens control alerting, and it's worth knowing which is which. Alert emails arrive as one consolidated digest per person per evaluation run, never one email per alert, and managed clients inherit their managing MSP's thresholds read-only. Both are separate from the QBR Pack's own auto-email schedule, which is specifically for the client report.
- 01
Settings → Organization → Advanced Settings — what counts as expiring
Sets the organisation-wide expiry/renewal lead time: how many days ahead something counts as "Expiring" or "Renewing Soon" (default 14 days, adjustable 1–365). The same window drives status badges, the Renewals report and the alert rules. This screen also holds the device lifecycle used for hardware end-of-life (default 3 years). Only the organisation's owner can change the lead time.
- 02
Settings → Alerts → My notifications — what reaches you
Your own subscription. A one-line profile at the top says what your settings amount to ("emailed about 16 of 17 emailable alerts, reminded weekly"), with three presets — Everything, Essentials (critical and warning alerts emailed, info-level ones in-app only) and Critical only — and a Custom state for anything hand-tuned. Delivery holds the global email switch, your reminder cadence (default weekly) and, in an MSP workspace, whether you cover all clients or only the ones you're assigned to. Below is the alert matrix: one row per rule with an In-app column and an Email column, so a switch always means "this channel, on or off". Each group heading carries a count like "4 of 5 emailed" and a "Turn all on" / "Turn all off" action for the whole section; filter chips and a search box narrow the list; the save bar lists exactly what Save will change. Non-admin members start with every Email switch off and opt in.
- 03
Settings → Alerts → Organisation rules — the thresholds
Admins tune the numbers behind each rule for the whole organisation, one card per rule: warranty-expiring lead time, the inactivity window before a licensed Microsoft 365 user counts as dormant (default 60 days, 1–365), the minimum unused seats before a licence is flagged (default 1), and how many quiet days a Microsoft 365 sync gets before it warns (2) or escalates to critical (5). Each threshold also shows on its row in My notifications as a read-only chip. A managed client sees its MSP's values read-only under a "Set by" banner. The end-of-life alert has no threshold of its own: it fires at the device lifecycle set under Settings → Organization, the same number behind end-of-life dates and the Hardware Lifecycle report.