The Compliance Alerts page lists every device that currently reports a status you’ve flagged as non-compliant. Use it as your daily triage queue.Documentation Index
Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
Use this file to discover all available pages before exploring further.
Open the alerts page
Go to MDM > Compliance Alerts. The list updates automatically each time a device syncs. There is no scan to launch and no acknowledge action — alerts appear when a device drifts and disappear when it returns to a compliant state.Default columns
| Column | What it shows |
|---|---|
| Status | The non-compliant status reported by the device (for example NOT_ENCRYPTED, OFFLINE_7_DAYS). |
| Control name | The MDM control or compliance rule that raised the alert. |
| Type | The rule category (encryption, OS update, antivirus, and so on). |
| Device name | The affected device. |
| Date | When Primo last evaluated the alert. The list is sorted most-recent first. |
Filter and customize the view
The Alerts page uses Primo’s table view system, so you can:- Filter by Device or Type.
- Show or hide columns to keep only the ones you care about.
- Save a filtered view for later reuse.
Inspect a device
Click any row to open the device drawer. From there you can:- Review the device’s full status across every compliance rule.
- Jump to the related MDM control to verify the configuration.
- Run remediation actions exposed by the device drawer (push profile, lock, wipe, and so on — see Manage your devices).
How alerts resolve
Alerts clear automatically. There is no manual acknowledge, snooze, or close. An alert disappears when:- The device’s status changes — encryption completes, the OS updates, the device comes back online, the missing profile is pushed.
- You remove that status from the rule’s non-compliant list. See Configure compliance alert rules.
Permissions
Viewing alerts requiresMDM_READ.
Next steps
- Configure compliance alert rules — adjust which statuses count as violations.