> ## Documentation Index > Fetch the complete documentation index at: https://docs.omnilinker.pl/llms.txt > Use this file to discover all available pages before exploring further. # Limits and retention > Merge duplicates, calm a runaway rule, cap emails per person, and choose how long notifications are kept. "Guard rails for the whole workspace: how much noise gets through, and how long history is kept." These settings apply to everyone in your organization. You need the **Manage limits and retention** permission, under **Notification Center**. Open **Notifications** > **How I get notified**, and under **Workspace**, choose **Limits and retention**. Change what you need and click **Save**, or **Discard** to throw your changes away. Next to each setting, a number shows its effect over the last week, such as "duplicates merged this week". ## Noise control | Setting | Default | What it does | | - | - | - | | "Treat the same alert as a duplicate if it repeats within …" | 5 min | "The same product, merchant and rule inside that window becomes one notification with a count, not a second one." Choose **off**, 1, 5, 10, 15, 30 or 60 minutes. | | "If one rule fires more than … times in an hour, bundle the rest into its digest, whatever people's settings say." | 50 | "Protects everyone from a runaway rule, for example after a large price import. Critical alerts still go out right away." 0 turns it off. | | "Never send one person more than … emails an hour. Past that, the rest stay in their bell." | 30 | "The bell is never limited." 0 turns it off. | The limit for the whole organization, emails per hour, is set on the email channel; see [Notification channels](/notifications/channels#how-email-is-sent). 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](/notifications/inbox#repeats-and-duplicates). A notification bundled by storm protection says "Bundled because its rule fired too often this hour." in its **Activity**. ## Retention | Setting | Default | What it does | | - | - | - | | "Keep notifications for …, then delete them." | 180 days | Choose 30, 90, 180, 365 or 730 days. "Anything still unacknowledged is kept until someone deals with it, however old it is." | | "Keep the delivery log (who got what, by which channel, and why it failed) for …" | 30 days | Choose 7, 14, 30, 90 or 180 days. Enough to answer “why didn't I get that email?”. The notifications themselves stay as long as set above. | 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-.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](/notifications/preferences#set-the-defaults-for-your-organization). * **How many escalation steps**: **Per policy**; see [Escalation policies](/notifications/escalation). * **Emails per hour for the workspace**: **On the channel**; see [Notification channels](/notifications/channels). The organization's email limit. What each person chooses for themselves. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.