Notification Manager

Notification Manager

Purpose

This page configures alert delivery and escalation routing so important events reach the right people without delay.

Prerequisites

  • Notification channels should be configured and available.
  • Team roles/owners should already be defined.
  • Users need permission to change tenant-level settings.

Main Actions

  • Configure notification rules by event type.
  • Set recipients, channels, and routing logic.
  • Adjust priority/escalation behavior.
  • Test and review notification outcomes.

Field/Status Reference

  • Event Type: Trigger source (for example alerts, incidents, reminders).
  • Recipients: Users or groups who receive notifications.
  • Channel: Delivery method such as email, SMS, or in-app.
  • Priority/Escalation: How quickly and broadly the event is routed.
  • Rule Status: Enabled/disabled state for each rule.

Workflow

  1. Select the event type to configure.
  2. Choose recipients and delivery channel(s).
  3. Define escalation logic for unresolved events.
  4. Save and validate with test events.
  5. Monitor delivery results and tune as needed.

Connections

  • Consumes events from alerting and operational modules.
  • Depends on up-to-date user ownership data from team pages.
  • Influences response speed in incidents and corrective workflows.

Common Mistakes

  • Sending all events to everyone, causing alert fatigue.
  • Missing escalation rules for high-severity issues.
  • Leaving old recipients after role or roster changes.

Troubleshooting

  • If notifications are not sent, verify rule status and channel configuration.
  • If recipients are wrong, review group membership and ownership mappings.
  • If volume is too high, refine event filters and escalation thresholds.

Quick Tips

  • Start with critical events, then expand coverage.
  • Review recipient lists after staffing changes.
  • Audit noisy rules monthly to reduce unnecessary alerts.