Rollout without an IT project
MDM or GPO for managed devices, BYOD activation for everyone else. A signed contract becomes a running deployment in days, not quarters.
The place most municipal care-tech dies is not procurement. It is rollout. A signed contract sits in a queue behind a quarter’s worth of IT-department priorities, some staff are issued devices, training is scheduled for a window that never quite arrives, and by the time the third shift is onboarded, the champion who signed the contract has already moved on. Clex sidesteps that failure mode by being available through two deployment channels in parallel: fully managed for devices the kommune’s IT already controls, and BYOD for everyone else.
Two channels, in parallel
- Managed deployment is the default for kommune-issued Android phones, kommune-issued iPads, and kommune-managed browsers.
- Android and iOS: the Clex Keyboard is installed through the kommune’s MDM (Intune, Knox, or any standards-compliant MDM) with a managed configuration that carries the licence key, the default language and, optionally, the organisation’s position on usage statistics. The care worker never sees the licence key.
- Chrome and Edge: the Clex Web extension is force-installed through GPO. Licensing and language preferences are controlled via the same managed policy.
- BYOD (Bring Your Own Device) is the safety valve. A care worker on a personal phone, a temp on a device that was never enrolled in MDM, a night-shift staffer on shared devices that haven’t been enrolled - any of them can activate Clex without IT involvement.
- The kommune administrator generates an activation code in the Clex Deployment Portal. The care worker receives the code, taps the deep link (or visits
byod.clex.aifor the browser extension), and Clex is active on that device. The activation code is exchanged for a licence key through the Clex API; the request carries the code and, like any internet request, the device’s IP address for the duration of the connection - nothing about the care worker. - In Clex Web, BYOD activation is refused when a managed licence key is already present, so a kommune with MDM cannot accidentally mix the two in the same browser.
- The kommune administrator generates an activation code in the Clex Deployment Portal. The care worker receives the code, taps the deep link (or visits
The Clex Deployment Portal
The Deployment Portal is the customer-facing side of rollout. Kommune administrators use it to provision licences, generate BYOD codes, configure available languages, and see what is deployed where. It runs on the same EU-hosted infrastructure as the Clex API. It holds the organisation’s licence records and the administrator accounts the kommune creates for it; it holds nothing about the care workers who activate Clex.
Why this matters for procurement
Two problems account for most stalled rollouts. The first is the device-fleet bottleneck: staff who need the tool do not yet have a device, or their device is not yet in MDM. The second is the mixed-fleet problem: permanent staff on kommune devices, substitute staff on personal devices, no single channel reaching all of them. BYOD solves both. The permanent staff get Clex through MDM the week the contract is signed; the substitute staff get Clex through an activation code the same week.
A rollout that reaches the full workforce in weeks, not quarters, reduces the cost of the pilot and shortens the time to value. Both deployment channels are available from the day the contract is signed.
Further reading
For the sixteen most common procurement, DPO, and IT-department questions, see the FAQ. Request the customer document pack from the compliance hub. To get in touch, visit the contact page.