Email Notifications — Transactional Alerts and Reports
What does the Email Notifications integration do?
Email delivers ZopNight alerts to a recipient address with no app or webhook to configure. It is the lowest-friction channel and the most limited: no cards, no interactive actions, and 2 layers of control apply: per-user email preferences sit on top of the channel's own event subscriptions.
Coverage by category
ZopNight uses email for the messages that must reach people even when chat is quiet: cloud alerts to organization admins, membership and role changes, team updates, scheduled report deliveries and export links. Every user controls per-event opt-outs; organizations on enterprise plans can route mail through their own SMTP sender for domain-aligned delivery.
Template-driven sends and one-hour signed links
Transactional email is template-driven and sent through ZopNight’s delivery service. Admin alert emails accompany critical cloud alerts (credential expiry, permission loss, sync failures) independent of chat channels. Recommendation shares and CSV/report exports arrive with signed links that expire after one hour. Custom SMTP senders (host, port, credentials, from-address) are provisioned per organization by ZopNight staff and validated with test sends.
Nothing to install, just toggle event groups
Nothing to install. To manage preferences: Settings > Notifications > Emails, toggle each event group. For custom SMTP delivery, contact support with your SMTP host, port and sender identity.
Alerts, lifecycle notices and expiring export links
Admin cloud-alert emails. User, role and team lifecycle notices. Report and export delivery with expiring links. Recommendation sharing by email. Per-event opt-outs. Optional tenant SMTP sender.
Two layers of control
A channel subscription decides which events are sent. Per-user email preferences then decide whether an individual receives them. Both must allow a message for it to arrive, which is why someone can be on a subscribed channel and still see nothing, because their own preferences are suppressing it.
Where it fits
Email is the right choice for digest-style awareness and for recipients outside the tools, such as a finance contact who needs budget breaches but has no reason to be in Slack. For anything time-sensitive, a chat channel gets read faster.
Limits worth knowing before you connect
Email is not a general alert-broadcast channel — chat channels (Slack, Teams, Google Chat, webhook) carry the full event stream. Self-service SMTP configuration is not exposed to customers.
Email Notifications integration: common questions
Someone on a subscribed channel is getting no email. Why?
Two layers must both allow a message. The channel subscription decides which events are sent, and that person's own email preferences decide whether they receive them. Their preferences are almost certainly suppressing it.
Can I configure my own SMTP server?
Not self-service. Custom SMTP senders (host, port, credentials and from-address) are provisioned per organisation by ZopNight staff and validated with test sends.
How long does an emailed export link stay valid?
One hour. Report and CSV export links, and shared recommendations, arrive as signed URLs that expire after that.
No active rule family targets Email Notifications — Transactional Alerts and Reports today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.