Manage delivery preferences and understand account-specific unsubscribe links.
Alarm rules determine when a condition exists. Email settings determine who receives its notifications. Changing one does not automatically change the other.
Review the recipient, selected sites, language and sending frequency together. The example address is not a real mailbox. Fictional demonstration data.
If loading fails, treat the list as unavailable, not as proof that it is empty. A recipient should disappear from management only after the server confirms removal. Local user profiles and automatic alarm-email recipients can be separate settings; inspect the relevant list when troubleshooting delivery.
Use recipient scope to direct relevant notifications to the people who can act on them. A fictional setup for the 360-site account could be:
| Recipient | Installation scope | Delivery cadence | Purpose |
|---|---|---|---|
| Operations | All 360 installations | Bundled, at most once per hour | Review newly reported issues across the account. |
| Maintenance | 90 explicitly selected installations | Bundled, per 24 hours | Review issues within that team's assigned site selection. |
The 90-site selection is explicit; it should not be read as an automatically synchronized portfolio assignment. Check the selected installations when responsibility changes. These are example delivery choices, not response-time guarantees or recommended schedules for every operation.
Three settings answer different questions:
Changing a recipient from a 24-hour bundle to an hourly bundle does not change a rule's threshold or make its measurements arrive faster. A problem becoming visible in the overview does not mean an email must arrive at that same moment.
For a custom alarm, also check the recipients selected in that rule. An empty recipient selection can leave the alarm visible in the overview without sending its email notifications. If recovery messages are wanted, check the custom rule's recovery option as well as the recipient's selected email content.
A follow-up task created in Alarm management has its own owner and reminder time. The reminder goes to that owner; it is not the same as a recurring account alarm bundle. A reminder task can remain open after its associated alarm has recovered.
If a message is unexpected, first identify whether it is an alarm bundle, a follow-up reminder or a scheduled report. Review the relevant recipient list or task instead of changing unrelated alarm rules.
The email-content configuration allows supported sections to be selected. Required information, including new alarms, the sender and the unsubscribe link, remains present. Keep the affected site, device and event time available to the person investigating the issue.
Recipients can use the unsubscribe link at the bottom of an automatic alarm email. It leads through the Eniris portal and identifies the account whose notifications are being stopped. Follow the confirmation on that page. The unsubscribe applies to that account's automatic alarm emails, not necessarily another account's notifications or report subscriptions.
Check which account sent it and whether it was already sent before the preference changed. Verify that the exact address is no longer selected for that account. An alias or forwarding mailbox can make the delivery address differ from the address displayed in your mail client.
If the unsubscribe page reports an invalid link, use a valid recent email or ask an authorized account administrator to check the recipient list. Keep report delivery settings separate from alarm subscriptions when investigating recurring messages.