Device group history not available: only current group assignment is stored per device

Android

Title: Device group history unavailable — only current group assignment is stored

When you look up a device in the Esper Console to review its group assignment history, only the current group is shown. There is no record of previous group assignments or reassignment events anywhere in the platform.

Why this happens

Esper stores only the device's current group assignment. Group reassignment events are not written to the Activity Feed or any internal audit log, and no historical record accumulates over time. This is a platform-level design constraint, not a misconfiguration.

View the current group assignment

Open the Esper Console and go to Devices & Groups.
Enter the device serial number in the search bar to locate the device.
Select the device to open its detail view.
Find the Group field in the device information panel. This displays the device's current group assignment only.

Verify: The Group field shows one group name — the device's present assignment. No history entries appear below it; this is expected behavior.

Track group assignment history outside Esper

Because no internal history exists, maintain an external record and update it each time you reassign a device in the Esper Console. Suitable options include:

A spreadsheet keyed on device serial number
A configuration management database (CMDB)
An asset management or IT service management (ITSM) system

Record the device serial number, previous group, new group, and timestamp at the moment of each reassignment. This external log becomes your audit trail.

What the Esper API returns

If you retrieve device details programmatically, the same limitation applies. The endpoint below returns only the current group assignment:

GET /v0/enterprise/{enterprise_id}/device/{device_id}/

No API endpoint returns group membership history. The device-level Activity Feed exposes events such as online/offline transitions and command execution results, but group reassignments are not included in that feed.

Request a feature

If your compliance or audit requirements depend on tracking group assignment history within Esper, submit a feature request to the Esper product team. Include your specific use case — for example, the compliance standard or regulatory requirement that mandates group history — so the team can assess priority accurately.

If this doesn't resolve it

If you are seeing unexpected behavior — for example, a device appears in a group you did not assign it to — that may indicate a separate issue rather than this limitation. Before contacting support, collect the following:

Device serial number and enterprise ID
The group name currently shown in the Esper Console
A description of the group assignment you expected to see
Approximate date and time the reassignment occurred

Contact Esper Support with these details so the team can investigate the device's recent activity.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.