Managing enrolled devices
Every signed-in app is an enrolled device: it holds a certificate for the encrypted tunnel, a registration for the user's extension, and data access for chat, voicemail and history. Admins see and control all of it in one place.
The device list
Admin → Connectivity → Mobile lists every enrolled device — which user it belongs to and its certificate status. Windows and mobile apps enroll through the same surface, and each appears with its platform and app version.
Revoking a device
Revoke a device when a machine is lost, retired or leaves the company. Revocation cuts off the device's calls and its data access together — its tunnel certificate stops being accepted and its registration ends. The user's other devices are untouched; signing in again on a new machine (or with a fresh pairing code) enrolls a new device.
Enrollment paths
- Credentials — the user signs into the app with the system's own sign-in options, including SSO.
- Pairing code — a one-time code minted from any signed-in web client's Provision apps button; works once and expires. Nothing to revoke if it's never used — it simply lapses.
Who can set up the app
By default users set up the app themselves, using either of the routes above. To keep device enrolment with administrators, untick Users can set up the Exovo app themselves under Connectivity › Mobile. With it off:
- the Provision apps button disappears from the header;
- signing in to the app with a password, or through the browser, is declined with a message asking the user for a pairing code;
- a pairing code an administrator issues still works — from QR Code on the user's page (Users › edit), or in the welcome email.
Devices that are already enrolled keep working. Revoke them below if they should not.