Updated on
May 12, 2026
Mark known violations as intentionally accepted to keep your MDG email digests focused on issues that still need attention.

When reviewing your data governance results, you may encounter violations that your team has already discussed and decided to accept — for example, a campaign name that intentionally deviates from the standard pattern. The Acknowledge Violations feature lets you mark these as reviewed so they stop appearing in email digest reports.
Acknowledged violations remain visible in the dashboard (with a distinct status), but they are filtered out of all future MDG digest emails for that workspace. Unacknowledging a violation immediately restores it to active status and includes it in future digests.
To acknowledge multiple violations at once, select them using the checkboxes and use the bulk Acknowledge action.
Hover over the acknowledgement checkmark in the violations table to see a tooltip showing which team member acknowledged the violation and when (displayed in your local time with timezone).
Each MDG digest email that contains hidden violations includes a link — "view in dashboard" — next to the acknowledgement note. Clicking the link opens the Data Governance Dashboard pre-filtered to the relevant rule and data source, with the page scrolled directly to the violations section.
The same pre-filtered link is also shown on the rule detail page, below the checks history:
|💡 You can acknowledge specific violations in the Data Governance Dashboard. Acknowledged violations will be hidden from email alerts.
Acknowledgements are shared across the workspace — anyone with the edit permission can see and act on them. When one user acknowledges a violation, it is hidden from all team members' digest emails for that workspace, not just their own.
Yes. Hover over the acknowledgement checkmark in the violations table to see a tooltip with the email of the team member who acknowledged it and the date and time it was acknowledged (shown in your local time with timezone).
The first acknowledgement is kept. Simultaneous acknowledges are safe — no duplicates are created and no data is lost.
An acknowledgement is tied to the specific combination of rule and entity. If the entity identifier reported by the data source changes, the existing acknowledgement will no longer match and the violation will reappear as active.
Editing a rule preserves its acknowledgements — the rule keeps the same internal identifier (SQL view name), so all existing acknowledgements remain in place. Deleting a rule and recreating it with the same name also preserves acknowledgements.
Improvado team is always happy to help with any other questions you might have! Send us an email.
Contact your Customer Success Manager or raise a request in Improvado Service Desk.