Before you start
The device must reach DG over the LAN. Device viewing/revocation permissions are required.
Steps
- Search by user, name or UID and check platform, version and last seen.
- Obtain pairing QR/address from configuration, set the App connection and sign in with a worker account.
- For lost or retired devices verify the target and revoke tokens; sign in again when reuse is intended.
Verify the result
The App can access the worker's assigned work and the last-seen time updates.
Notes and examples
A phone's own 127.0.0.1 is not the server. Use a reachable LAN address and numeric port.
Limitations
TOTP-enabled accounts cannot use device login. App DG access requires Std or above; DG itself does not check subscriptions.
Troubleshooting
Check network, server address, port, firewall and account first. For missing work check its worker assignment; never include passwords in reports.
Frequently asked questions
What is Devices for?
Find mobile devices, last activity and token state, and revoke access when needed.
What do I need before using Devices?
The device must reach DG over the LAN. Device viewing/revocation permissions are required.
How do I use Devices?
Search by user, name or UID and check platform, version and last seen. Obtain pairing QR/address from configuration, set the App connection and sign in with a worker account. For lost or retired devices verify the target and revoke tokens; sign in again when reuse is intended.
How do I verify the result in Devices?
The App can access the worker's assigned work and the last-seen time updates.
What should I keep in mind in Devices?
A phone's own 127.0.0.1 is not the server. Use a reachable LAN address and numeric port.
What are the limitations of Devices?
TOTP-enabled accounts cannot use device login. App DG access requires Std or above; DG itself does not check subscriptions.
How do I troubleshoot Devices?
Check network, server address, port, firewall and account first. For missing work check its worker assignment; never include passwords in reports.