Cloud Push where hardware supports it
Add the device serial, generate a device-specific pairing key, and configure the device's Cloud Server or ADMS setting to send attendance securely.
Biometric attendance
Connect supported Cloud Push devices, legacy local-network devices or USB exports while keeping biometric templates on the physical device.
What it does
OPleo keeps the workflow connected without claiming to replace every specialist system. The focus is a dependable operational record that the right person can act on.
Built into OPleo
Add the device serial, generate a device-specific pairing key, and configure the device's Cloud Server or ADMS setting to send attendance securely.
For devices that cannot push to the cloud, an office-network connector reads device logs without exposing the device's private address publicly.
Test and sync results explain unreachable devices, archived-only logs, unmapped PINs and the next practical resolution.
How the workflow holds together
Each feature uses the organisation, employee and policy information already in the workspace. That reduces repeated entry and gives people the context they need before they decide or approve something.
Use Cloud Push for ADMS-capable hardware, a connector for LAN-only hardware, or USB import for history.
Save every enrolled user ID against the matching employee.
Use last activity, sync results and unmatched ID summaries to fix the real issue quickly.
Questions teams ask
No. OPleo works with device user IDs and attendance punches, not fingerprint or face templates.
Yes. Wi-Fi and Ethernet both work when the selected connection path can reach the device.