Per‑User Email Opt‑In vs Digest Email: Which to Enable for Sulu Notification Noise?

Goal

Reduce notification noise in Sulu CMS while preserving per‑event granularity for content creation, publish, and workflow transitions.

Current Constraints

Sulu offers two native channels: dashboard alerts visible in the admin UI and immediate email notifications sent to all users with a relevant role. The admin UI lacks per‑role or per‑user overrides, so every subscribed user receives the same notification format. Custom Symfony event subscribers can suppress or modify notifications on a per‑user basis, but this requires code changes.

Unresolved Decision

Community discussions have not reached consensus on whether to implement a per‑user opt‑in setting for email notifications or to rely on a single digest email that aggregates events. Each approach has trade‑offs in terms of system performance, timeliness of alerts, and developer effort.

Questions

• What are the performance implications of enabling per‑user email opt‑in versus generating digest emails for a large user base?
• Does the digest approach compromise the timeliness of critical alerts compared to immediate per‑event emails?
• Are there existing community plugins or documented patterns that support per‑user opt‑in without custom code?