MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Automation

Notification Management

The delivery and record of notifications across channels — in-app, email, push and SMS.

Where you will find this

Notifications & channels.

Purpose

Other modules (alerts, webhooks, the execution engine) raise notifications; this module records them, tracks their status through to read, and delivers them on the channel you prefer.

The Notification Management module provides a central business capability for creating, managing and delivering business notifications to authorised recipients through supported communication channels.

It enables consistent, configurable and timely communication of business information generated across the platform.

The module serves as the platform-wide notification delivery capability.

Objectives

The module will:

  • Generate business notifications.
  • Manage notification templates.
  • Determine notification recipients.
  • Deliver notifications through supported channels.
  • Track notification delivery status.
  • Maintain notification history.
  • Support user notification preferences.

Functional Scope

The module includes:

  1. Notification Definition
  2. Notification Template Management
  3. Recipient Management
  4. Channel Management
  5. Notification Delivery
  6. Delivery Tracking
  7. Notification Preferences
  8. Notification History
  9. Notification Audit

Notification Model

A notification represents the communication of business information to one or more authorised recipients.

Notifications may originate from:

  • Alerts
  • Business Events
  • Scheduled Activities
  • Business Processes
  • System Activities

A notification remains independent of the business event that created it.

Notification Definition

The platform will support multiple notification categories.

Typical categories include:

  • Trading Notifications
  • Portfolio Notifications
  • Strategy Notifications
  • Risk Notifications
  • Market Notifications
  • System Notifications
  • Administrative Notifications
  • Integration Notifications

The design will support additional notification categories.

Notification Templates

The platform will support reusable notification templates.

Templates may define:

  • Notification Title
  • Notification Content
  • Notification Category
  • Delivery Priority
  • Supported Channels

Templates remains configurable.

Recipient Management

The platform will determine authorised notification recipients.

Recipients may include:

  1. Individual Users
  2. User Groups
  3. Portfolio Owners
  4. Strategy Owners
  5. Administrators
  6. Operational Teams
  7. External Systems

Recipient determination will support business rules.

Channel Management

The platform will support multiple notification delivery channels.

Typical channels include:

  1. In-Application Notification
  2. Email
  3. SMS
  4. Mobile Push Notification
  5. WhatsApp
  6. Telegram
  7. Microsoft Teams
  8. Slack
  9. Webhook

The design remains extensible.

Notification Delivery

The platform will deliver notifications through one or more configured channels.

Delivery processing includes:

  • Recipient Resolution
  • Channel Selection
  • Delivery Initiation
  • Delivery Status Recording

Notification delivery will support multiple channels for the same notification.

Notification Preferences

The platform will support recipient-specific notification preferences.

Preferences may include:

  • Preferred Channels
  • Notification Categories
  • Delivery Timing
  • Priority Thresholds
  • Quiet Hours

Preferences will influence notification delivery.

Delivery Tracking

The platform will track notification delivery.

Tracking may include:

  • Pending
  • Delivered
  • Failed
  • Read
  • Acknowledged

Delivery history remains available.

Notification History

Historical notification records is preserved.

History includes:

  • Notification Category
  • Recipient
  • Delivery Channel
  • Delivery Status
  • Delivery Timestamp

Historical records remains immutable.

Business Rules

  • Every notification will have a unique identifier.
  • Every notification will belong to one notification category.
  • Every notification will have at least one authorised recipient.
  • Every notification will use one or more supported delivery channels.
  • Notification delivery is tracked.
  • User preferences is respected where applicable.
  • Historical notification records will never be deleted.

Audit Requirements

The platform will maintain an audit trail for notification activities.

Audit events includes:

  • Notification Creation
  • Recipient Resolution
  • Delivery Initiation
  • Delivery Success
  • Delivery Failure
  • Notification Read
  • Notification Archive

Audit records remains immutable.

Out of Scope

The following are outside the scope of this module:

  • Alert Generation
  • Business Rule Evaluation
  • Strategy Execution
  • Order Execution
  • Portfolio Valuation
  • Market Data Processing

These responsibilities belong to their respective business modules.