MCM-19 — MSP-Level Notifications

← Back to Notification System overview

As an MSP Admin,
I want to receive notifications when any enterprise tenant under my management experiences a critical event (billing failure, account sync error, subscription expiry warning),
so that I can proactively support tenants without waiting for them to contact me.

Acceptance Criteria

• MSP Admins receive a separate notification feed scoped to MSP-level events (not enterprise-internal events).
• Notification types available to MSP Admins include: enterprise billing failure, subscription expiry (30-day and 7-day warnings), enterprise account sync failure (repeated 3+ times), new enterprise onboarding completed, and an enterprise account being activated or deactivated.
• Enterprise account activation/deactivation is a tenant-level state change, distinct from an individual user being activated or deactivated within a tenant (see the Notification Categories table's User Management row) — only the tenant-level event appears in this feed.
• MSP Admins can configure channel preferences independently for MSP-level and enterprise-level events.
• MSP-level events are clearly labelled with the affected enterprise name in the notification title and body.

---

Technical Design

This feed reuses the same delivery channels as tenant-level notifications (MCM-14 — Real-Time In-App Notification Bell, MCM-16 — Web Push Notification, MCM-17 — Email Notification), filtered to a fixed set of MSP-only event types (billing failure, 30-/7-day expiry warnings, repeated sync failure, onboarding completed, account activated/deactivated) via a separate GET /api/msp/notifications feed, distinct from the tenant-scoped GET /api/notifications. MSP-level and enterprise-level preferences are stored and configured independently through PUT /api/msp/notification-preferences — enabling or disabling one has no effect on the other, even for the same MSP Admin account (see MCM-18 — Notification Preferences). Every MSP-level event is always labelled with the affected enterprise's name in its title and body.

---

UI / Frontend Changes

• New MSP Admin feed/screen, separate from the standard notification bell drawer, listing MSP-scoped events labelled with the affected enterprise name.
• Independent channel-preference controls for MSP-level events, distinct from the enterprise-level Notification Preferences matrix.
• Notification entries for this feed surface the affected enterprise name prominently in both title and body text.