--- title: "Configuring Email Notifications" slug: "configuring-email-notifications" updated: 2025-04-29T20:32:23Z published: 2025-04-29T20:32:23Z canonical: "docs.serenityops.com/configuring-email-notifications" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.serenityops.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Email Notifications **Email notifications** in Serenity help ensure that the right team members are alerted as soon as an incident is reported or updated. This improves response time, accountability, and communication across your EHS program. --- ## Default Email Behavior Out of the box, Serenity sends email alerts in the following scenarios: - 📥 **When an incident is reported** - The **assignment group** and/or **assigned user** will receive an email notification - 🔄 **When an incident is reassigned** - The **newly assigned group or user** will be notified of the change These notifications help ensure that assigned teams are made aware of new or redirected responsibilities **without requiring manual follow-up.** --- ## Custom Email Notifications (Optional) Need more tailored alerts? The **Serenity Services Team** can help configure **custom if/then email rules** based on your organization’s needs. Examples include: - "If category = Injury AND severity = High → notify Regional Safety Director" - "If an injury is flagged as Recordable → alert HR & Compliance" - "If incident type = Vehicle Damage → notify Fleet Manager" 📞 To set up custom notification logic, contact your Serenity Customer Success or Support representative. --- ## 🚧 Coming Soon: Self-Service Notification Settings A **notification configuration page** is coming soon, allowing **EHS Admins** to: - Define new notification conditions - Choose recipients (groups, roles, individuals) - Set notification frequency and triggers - Enable/disable specific default alerts This will allow safety teams to maintain their own alerting logic without relying on support tickets. --- ## ✅ Best Practices

Always route notifications to groups, not individuals, to prevent gaps in coverage
Avoid over-notification — keep rules focused to ensure users take action
Review email rules when updating your assignment rules