MCM-46 — FinOps New Recommendation Notification
Notify when a new cost-saving recommendation is generated, with a "new" indicator that outlives the notification itself.
MCM-46 — FinOps New Recommendation Notification
← Back to Notification System overview
As a FinOps User,
I want to be notified when a new cost-saving recommendation is generated, and be able to tell it's new wherever I later come across it,
so that I don't have to keep re-checking the recommendations list on the chance something changed, and I don't lose track of what's genuinely new once I've dismissed the notification itself.
Acceptance Criteria
- When a new cost-saving recommendation is generated, a notification is sent naming the type of recommendation and its estimated savings.
- Each recommendation carries its own "new" indicator that is separate from the notification's read/unread state — marking the notification as read does not clear the recommendation's "new" indicator.
- The "new" indicator on a recommendation only clears once the user opens that recommendation itself, whether they got there via the notification or by browsing the recommendations list directly.
- A recommendation that is still open from an earlier run is not re-notified on every subsequent check — only newly generated recommendations trigger a notification.
- The recommendations list itself (independent of the notification bell) visibly distinguishes recommendations still marked "new" from ones the user has already opened.
Technical Design
When FinOps's recommendation logic generates a new cost-saving recommendation, it is flagged "new" on the recommendation itself and, at the same time, raised as a notification through the same categorized delivery pipeline every other notification type uses. The "new" flag lives on the recommendation, not on the notification, so it persists and remains visible in the recommendations list regardless of whether the notification was ever read, and it only clears when the user actually opens that recommendation. A recommendation still open from a previous run is not re-notified.
UI / Frontend Changes
- FinOps recommendations list shows a "New" badge on any recommendation the current user hasn't opened yet, independent of the notification's own read state.
- The recommendation notification deep-links directly to that recommendation in the list.
- The "New" badge clears only when the recommendation itself is opened — dismissing or reading its notification does not clear it.
MCM-45 — Module Usage Plan Threshold and Expiry Notifications
Warn when a module's own usage plan nears or hits its limit, independent of the enterprise's overall subscription.
MCM-20 — Custom Tag Improvements
Overview, personas, and architecture for the Custom Tag Improvements initiative — allowed-list reconciliation, resource-view editing, and topology-driven tag suggestions.