Skip to main content

Using the Devices Page Day-to-Day

How to read the Devices table, what each compliance check means, and how to upload evidence when a provider can't report a check automatically.

Written by Upendra Varma

Manage → Organisation → Devices is your inventory of every employee device ComplyJet is tracking, pulled in from an MDM integration, the ComplyJet Agent, or added manually.

Reading the table

  • All / Compliant / Non-Compliant / Others tabs filter the list. "Others" is devices your MDM previously reported that have since been removed upstream.

  • Three checks appear as columns: Encryption, Anti-Virus, and Screen Lock. A device is compliant only when all three pass.

  • A dash () means the check is Unavailable — the connected provider doesn't report that signal, not that the device failed it. Unavailable checks count as passing for compliance purposes.

Opening a device

Click any row to see the detail drawer, with one panel per compliance check:

Each panel shows the status your provider (MDM or the ComplyJet Agent) reported, plus a place to upload manual evidence — a screenshot or export proving the check passes another way. Manual evidence only fills the gap when a provider genuinely can't report that check; it doesn't override a provider's own verdict if one already exists.

Where a device came from matters

Devices behave differently depending on their source, shown in the Provider column:

  • MDM-sourced devices (Intune, Kandji, Jamf, etc.) are read-only here — edit them at the MDM itself.

  • Agent-tracked devices can be deleted from ComplyJet, but deleting them here doesn't uninstall the agent — the device can reappear on the next sync if the agent is still running.

  • Manually added devices are fully editable and deletable.

Why is my device marked non-compliant?

Start with the detail drawer — one of the three checks is failing or missing evidence. If a check shows Unavailable rather than a clear pass/fail, that's a provider limitation, not a compliance failure, and won't be what's dragging the device into Non-Compliant.

Did this answer your question?