Notification Management Domain

Overview#

A platform serving law enforcement and utility operations generates a constant stream of internal notifications: investigation updates, evidence uploads, assignment changes, and system alerts. Without proper controls, analysts quickly learn to ignore them all. The Notification Management domain gives users fine-grained control over what they receive, when they receive it, and through which channel, keeping relevant signals visible and noise suppressed.

Key Features#

• User notification preference management with per-type granularity
• Notification template system with variable substitution and multi-channel formatting
• Bulk notification delivery to targeted user groups
• Quiet hours configuration to suppress non-critical notifications
• Read and unread tracking with mark-as-read operations
• Multiple delivery channels: in-app, email, push, and SMS
• Support for notification types including investigation updates, evidence uploads, mentions, assignments, and alerts

Use Cases#

Relevant sectors include law enforcement, critical infrastructure, and intelligence agencies.

• Delivering in-app notifications for investigation updates and evidence uploads
• Managing user notification preferences to reduce alert fatigue
• Sending bulk notifications to teams about system alerts or assignments
• Configuring quiet hours to prevent non-critical notification delivery outside working hours

Integration#

The Notification Management domain integrates with Notification for mass emergency alerting, Alert for system alerts, Email for email delivery, and User for preference management and recipient targeting.

Open Standards#

• GraphQL (June 2018 specification): All notification preferences, templates, and delivery operations are exposed through a typed GraphQL API using queries and mutations, enabling interoperable client integrations.
• JSON Web Token, RFC 7519: Service-to-service calls, including delayed-delivery queue submissions, are authenticated using RS256-signed JWTs issued by the platform's ServiceJWTClient.
• OAuth 2.0, RFC 6749: Push notification delivery via Firebase Cloud Messaging uses the OAuth 2.0 service-account JWT bearer flow to obtain short-lived access tokens from Google's token endpoint.
• SMTP, RFC 5321 / MIME, RFC 2045: The email delivery channel uses standard SMTP submission with MIMEMultipart and MIMEText message construction, supporting both plain-text and HTML alternative bodies.
• ISO 8601: All notification timestamps, creation time, read time, expiry, scheduled delivery, and queue message fields, are serialised as ISO 8601 date-time strings.
• IANA Time Zone Database: Quiet-hours windows are evaluated in the recipient's named timezone via the IANA TZDB (zoneinfo), ensuring correct overnight-spanning suppression across all global locales.
• Traffic Light Protocol (TLP, FIRST standard): Notification content is gated against the platform's TLP-aligned SecrecyLevel classification ranks (TLP:WHITE through TLP:RED), ensuring recipients only receive notifications at or below their clearance level.

Last Reviewed: 2026-02-05 Last Updated: 2026-04-14