NounDeskDevice status
NounDesk describes every device in four separate ways. A phone can be Online but Needs attention, or Compliant but Offline, so each one has its own badge.
Who: all roles.
| Dimension | Answers the question | Where it comes from |
|---|---|---|
| Lifecycle | Where is the device in its life with us? | Stored by NounDesk, updated by Google’s reports and your actions |
| Connectivity | How recently was it in touch? | Worked out from Last seen |
| Compliance | Does it follow its security policy? | Reported by the device through Google |
| Trust | Can we trust it with company data? | Worked out from the device’s security reports |
Lifecycle
| Badge | What it means and what causes it |
|---|---|
| Waiting for device | You generated an enrollment code and NounDesk is waiting for a device to scan it. If the code expires unused, the entry is retired automatically. |
| Setting up | The device has scanned the code and checked in, and is finishing setup. |
| Active | The device is managed and in normal use. |
| Lost mode | You turned on lost mode. The device is locked and shows your message. End lost mode returns it to Active. |
| Disabled | Google reports the device as disabled. |
| Erasing… | You sent Erase device and NounDesk is waiting for the device to confirm. If the erase fails or expires, the device goes back to Active. |
| Erased | The erase finished and the device is no longer managed. It also appears if Google stops listing the device, for example because it was removed from management outside NounDesk. |
| Retired | You retired the device. It leaves the active list; its history stays in the audit log. |
A device usually moves Waiting for device → Setting up → Active. It can go to Lost mode and back, and at the end of its life to Erasing… → Erased → Retired. Only a device that’s Erased or still Waiting for device can be retired. See Retire and offboard.
Connectivity
Worked out from the last time the device checked in (Last seen):
| Badge | Rule |
|---|---|
| Online | Seen in the last 15 minutes. |
| Recently offline | Last seen between 15 minutes and 24 hours ago. |
| Offline | Last seen more than 24 hours ago. |
| Not seen yet | Has never checked in. |
On the dashboard, the Offline tile counts devices that are Offline or Not seen yet. Recently offline devices are counted in neither Online nor Offline.
Compliance
Reported by the device each time it checks in:
| Badge | What it means |
|---|---|
| Compliant | The device follows its policy. |
| Needs attention | At least one problem is stopping the device from following its policy, for example an app failed to install or a setting needs newer Android. |
| Attention | Only small, usually temporary issues: an app still installing, a setting still being applied, a blocked app waiting to be removed, or something the employee needs to do. |
| Unknown | The device hasn’t sent a report yet. |
Open the device’s Security tab to see each issue and what to do. See Fix compliance issues.
Trust
Trust rates whether the device itself is safe: Trusted, At risk, Not trusted or Not reported yet. It looks at things like system integrity, encryption and security update age. See Device trust.
How these feed the dashboard
The dashboard’s Fleet health chart combines lifecycle, connectivity, compliance and Google’s security check into Healthy, Needs attention or Critical. See Fleet health rules.