Monitoring Alerts SettingsCopy Anchor Link

Monitoring Alerts settings control which changes generate alerts for your team and how those alerts are delivered. You find them under Settings → Monitoring alerts in the app; they can be adjusted by team managers.

The page is organised into five sections, and a sixth for teams with custom screening lists:

1. Show Monitoring Alerts view — controls whether the Monitoring page is visible in the app
2. PEP alerts
3. Sanctions alerts
4. Relation alerts — roles, owners, ownership, and beneficial owners
5. Company Information alerts — registry data, financials, lifecycle status, and court cases
6. Custom screening list alerts — hits on your team's own lists of company names

Each category has its own master toggle, granularity options, and email-notification settings. Changes apply to your whole team.

Show Monitoring Alerts ViewCopy Anchor Link

Controls whether the Monitoring page is visible in the app for your team.

When disabled, the page is hidden from the sidebar for everyone on the team. Some API-first teams choose this so that alerts don't sit unresolved in an interface they rarely open — alerts remain available over the Connect API and email notifications still go out if enabled. Use it with care: it removes the Monitoring view for your entire team.

PEP Alert SettingsCopy Anchor Link

Master ToggleCopy Anchor Link

Enable or disable PEP monitoring alerts entirely.

Alert GranularityCopy Anchor Link

Choose one of two modes:

Alert on Hits Found When an Entity Is Added to MonitoringCopy Anchor Link

By default, the first screening of an entity you add to monitoring sets its baseline: hits it already has at that point are recorded but don't alert, and only later changes do. Turn on Alert on hits found when an entity is added to monitoring to be alerted about those hits too.

When the toggle is on, a company or private person added to monitoring since the previous completed full monitoring run gets an alert if its first screening shows it as a PEP or RCA. If your team alerts on PEP/RCA status changes, your PEP and RCA status choices decide which of the two count; if it alerts on individual hits, both count. The alert looks the same as any other PEP alert.

An entity that was removed from monitoring and then added again does not get this alert. The toggle is off by default.

Email NotificationsCopy Anchor Link

Optionally deliver PEP alerts by email — see Email delivery below for how and when emails are sent.

Sanctions Alert SettingsCopy Anchor Link

Sanctions alerts follow the same pattern as PEP alerts:

• Master toggle — enable or disable all sanctions alerts.
• Granularity — either changes in screening hits (added / changed / removed, all enabled by default) or sanctioned status change (a single toggle that alerts when an entity gains or loses its sanctioned status).
• Alert on hits found when an entity is added to monitoring — off by default. When on, an entity added to monitoring since the previous completed full monitoring run gets an alert if its first screening has a suggested true positive sanctions hit, on the entity itself or on its related entities, as with other status alerts. If your team uses sanctioned status alerts and has turned off the sanctioned status alert, it does not alert. It works as described for PEP alerts, including that an entity added again after being removed does not get the alert.
• Email notifications — per-category email delivery.

Relation Alert SettingsCopy Anchor Link

Relation alerts cover changes in the ownership and role structure of monitored companies. One master toggle, four independent sub-categories:

• Role exclusion list — exclude specific role titles from triggering alerts (for example Auditors and Accountants, if those changes aren't relevant to your team). With no exclusions, all role changes alert.
• Ownership thresholds — only alert when the stake involved is at least the threshold percentage. For owners the minimum is 5% (owners below 5% are not part of the ownership data). For ownership and beneficial owners the range is 0–100%.
• Beneficial owners identified without an ownership percentage (for example through family relations or roles) are not affected by the threshold — they always alert while beneficial-owner alerts are enabled.

Company Information Alert SettingsCopy Anchor Link

Company Information alerts cover changes to a monitored company's registry data, financial figures, lifecycle status, and court cases.

The master toggle is disabled by default. When you first enable it, the next monitoring run establishes a baseline for your portfolio — enabling it on a large portfolio may produce an initial wave of alerts.

With the master toggle on, these fields alert by default:

These fields are opt-in (disabled until you enable them):

There is also a separate toggle for alerting on company-information changes in related companies (disabled by default).

Custom Screening List Alert SettingsCopy Anchor Link

Custom screening list alerts tell you when a monitored company, or a company in its screening scope, gets or loses a hit on one of your team's custom screening lists.

• Enable custom screening list alerts: on by default.
• Alerts in the monitoring view and Alerts over email: choose where the alerts go. Email uses the same recipient modes as the other categories; see Email delivery.

Monitoring screens every list your team has uploaded, whether or not the list is in a calculated risk score level. Which companies around the monitored company are screened follows the Screening scope on the Custom screening lists settings page; see Screening Scope. Uploading a new version of a list alerts only on the hits it adds or removes.

Previewing Changes in Draft ModeCopy Anchor Link

One draft spans the PEP, Sanctions, Geographic & Structural, Monitoring alerts and Calculated Risk settings pages. Calculated Risk changes have no preview yet; see Staging Changes in Draft Mode.

When draft mode is on, each alert category shows a live preview of what your changes would do before you apply them. The preview compares the alerts your active (current) settings produce against what your draft settings would produce, counted over a recent window of real changes to your portfolio.

• A headline shows the active → draft alert volume, as a total or an approximate per-week / per-month rate. A rate is only offered once the window covers a full week or month; otherwise it shows the total.
• Per-field bars break the volume down by change type. Hovering a bar shows how its total splits into kept, added, removed, and never alerts.
• For PEP and Sanctions, the two granularity options are shown side by side so you can compare them without switching the radio. The option you haven't selected is greyed out as a "what if".
• The preview only covers what monitoring screens. Monitoring itself does screen a private person's connected network for PEP and sanctions, following the team's private-person screening settings — but the preview here does not yet reflect those network changes, so the connected-entity settings under private-person screening move no number in this preview. They do take effect in reviews, risk factors, risk summaries and adverse media search, and each of those settings says so on itself when you change it. For the same reason the private-person role breakdown shows a bar for the person themselves only; the connected-role bars are left out rather than drawn empty. High-risk industry and high-risk legal form are properties of a company, so a private person can only match them through a connection: those two panels say so outright instead of reporting an empty result.

Applying a draft opens a summary of every change with its projected alert-volume impact per category. These figures are projections from recent history; alerts typically spike right after a change, then settle.

The same summary takes a free-text reason for change, recorded with the new version in the Settings Change Log. Every draft needs one, whatever it changes: Apply changes stays disabled until a reason is entered.

When Someone Else Changes the Settings While You Have a DraftCopy Anchor Link

A draft survives a settings change made by someone else after you started it. Your draft is a list of individual setting changes, and applying it lays that list over whatever is live at the time — so their changes stay on every setting your draft does not touch.

Where the two overlap, the apply summary says so before you commit:

• A setting they changed to something else is called out by name in a warning, and applying your draft replaces their value with yours. The change overview shows the value that is live now on the left, so you can see exactly what you would be overwriting.
• A setting they changed to the value you had already staged needs no work: it is left out of the change count and applying it does nothing. If every change in your draft has already been made this way, there is nothing left to apply and the draft can simply be discarded.

Email DeliveryCopy Anchor Link

Each alert category has its own email setting, disabled by default. When enabled, choose one recipient mode per category:

Emails are sent as a daily digest: one consolidated email per user per team, covering unresolved alerts from the last seven days that haven't already been emailed. Email delivery requires monitoring access to be enabled for the team. Hiding the page with Show Monitoring Alerts view does not stop these emails.

Default SettingsCopy Anchor Link

All teams start with the following defaults:

If your team was migrated to the new monitoring system on default settings in 2026, this table is what you received — every value can be changed on this page.

Related PagesCopy Anchor Link

• The Monitoring System — how monitoring and screening actually run
• Working with Monitoring Alerts — the day-to-day alert workflow
• Monitoring Alerts over the API — consuming alerts programmatically
• PEP Settings and Sanctions Settings — screening configuration that determines what counts as a hit (changing these can generate new alerts)