Noise control
The limit for the whole organization, emails per hour, is set on the email channel; see
Notification channels.
Storm protection counts notifications, not alerts: every person’s copy counts, so a rule that notifies three people
adds three to the count each time it fires. A rule here is whatever groups notifications together, such as one alert
rule, one warehouse’s stock alerts or one print station.
How a duplicate looks in the inbox is described in
Notification inbox. A notification bundled by storm protection says
“Bundled because its rule fired too often this hour.” in its Activity.
Retention
Omnilinker deletes once a night, at 03:00 UTC: 04:00 in Poland in winter and 05:00 in summer. A notification is
deleted when it is older than the period and was acknowledged, was resolved at its source, or was hidden by someone’s
never tell me exception. The number next to the setting shows how many “will be deleted tonight at 03:00”; that
time is UTC too.
Export before cleanup
The card Stored today shows how many notifications are kept, a bar for each month, and the date of the oldest. To keep a copy of what will be deleted next, click Export before cleanup (CSV). The file,notifications-before-cleanup-<date>.csv, has the columns CreatedUtc, UserId, Source, Type, Severity,
Title, Body, UserState, AcknowledgedUtc and ActionUrl, up to 50,000 rows. The button is greyed out when
nothing is due for deletion.
Handled by Omnilinker
The card Handled by Omnilinker lists what you do not set here:- How often digests and escalations are checked: Every minute.
- Batch size for sending: Automatic.
- Default quiet hours: on Defaults for new users; see How I get notified.
- How many escalation steps: Per policy; see Escalation policies.
- Emails per hour for the workspace: On the channel; see Notification channels.
Notification channels
The organization’s email limit.
How I get notified
What each person chooses for themselves.