ALT · Alerts & Notifications
Email notification preferences
Choose what lands in your inbox, and when things count as expiring.
4 min read
Three settings control alerting, and it's worth knowing which is which. Alert emails arrive as one consolidated digest per person per run — new, still-open and resolved alerts grouped together — never one email per alert, and managed clients inherit their managing MSP's thresholds read-only. All of this is separate from the QBR Pack's own auto-email schedule, which is specifically for the client report.
- 01
Settings → Organization → Defaults — what counts as expiring
The expiry & renewal alert window sets how many days ahead something counts as "Expiring" or "Renewing Soon" (default 14 days, adjustable 1–365); certificates have their own warning times — see Organisation rules below. Days are whole calendar days: something due on 14 November is due all of that day and overdue from the 15th, and "within 14 days" means today through the 14th day. 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 owner can change these — for a managed client, its MSP's owners and admins can too.
- 02
Settings → Alerts → My notifications — what reaches you
Your own subscription. A one-line profile at the top says what your settings amount to ("You'll be emailed about 22 of 22 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 Alert emails switch, your Reminder cadence (every 3 days, weekly — the default — every 2 weeks or monthly; it's also how long "My reminder interval" acknowledges an alert for) and, in an MSP workspace, the Client scope you're emailed about — all managed clients for admins, your assigned clients for everyone else. 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"; a few rules are in-app only. MSP owners, admins and technicians also get a My queue column that decides which alerts land on their work list. 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 Find an alert box narrow the list; the save bar lists exactly what Save changes. Non-admin members start with every Email switch off and opt in. At a managed client everyone starts opted out, admins included, and a read-only contact has no notification settings.
- 03
A shared alerts mailbox (optional)
Delivery also has a Shared mailbox: one address, such as alerts@yourcompany.com, that receives every alert email about the organisation — in an MSP workspace, the workspace and all its managed clients — whatever anyone's own switches say, with weekly reminders. Owners and admins set it (for a managed client, the MSP's owners and admins can too); everyone else sees it read-only once it's set.
- 04
Settings → Alerts → Organisation rules — the thresholds
Owners and admins see this second tab (a technician sees it read-only on a client assigned to them) and tune the numbers behind the rules for the whole organisation, one card per rule that has a threshold: warranty and licence renewal lead times (both follow the alert window by default), certificate warning times by type (code signing 45 days, CA certificates and certifications 90, everything else the alert window), 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), how many quiet days a Microsoft 365 sync gets before it warns (2) or escalates to critical (5), and the timing of the leaver and account-status rules. Once you change a threshold, a Reset button beside it puts it back to the default, and each threshold also shows on its row in My notifications as a read-only chip. At a managed client the tab opens with a "Set by" banner naming the MSP: MSP staff see the inherited values read-only, and the client's own admins are pointed to the MSP if a threshold needs changing. 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.