How do last-seen timestamps work in Skie?

Skie for Enterprise · Updated

Short answer

Each device carries a last-seen time, updated whenever it reports in, either through a full sync or the regular presence report. The dashboard shows it per device and uses it to decide whether the device is Due, Overdue, Offline unusual or in breach. It tells you when Skie last heard from the device, not what the user is doing.

The last-seen timestamp answers a simple question: when did this device last tell Skie it was alive? It is refreshed by any check-in, whether that is a full sync or the lightweight presence report about every 4 minutes. A device that is switched on and connected will normally show a recent time.

You will find it on the device page, in lists of devices and in the breach centre. Staff can sort or filter by it to find the quietest devices first. The thresholds that turn a long gap into Due, Overdue, Offline unusual or Breach are editable, so what counts as long is your decision.

Timing is taken from a trusted clock rather than the device's own clock, so a wrong or changed time on the tablet does not distort the figure. Date and time on managed devices are also locked to automatic.

What a stale last-seen time can mean: the device is off, flat, out of coverage, in offline mode, or in a bag with the screen off on a model whose power management is aggressive. It does not by itself prove misuse. Skie does not read private messages and the timestamp carries no content.

If the same device repeatedly goes quiet, look at its pattern rather than one reading. Offline unusual exists for that purpose, comparing a device with its own normal behaviour.

Practical tip: sort by last seen on Monday morning. Anything old after a normal charging cycle is the short list to check first.