Device enrollment
How a device joins your tenant, what consumes a license seat, and where enrollment state lives.
Before you enroll
- Customer portal accessDevice enrollment starts in the customer portal for the site the device belongs to.
- A seat availableRegister devices up to the purchased seat quantity. A device in pending enrollment does not consume a seat, so you can prepare hardware first.
- Backend billing stateDevice entitlement is granted only from verified backend billing state — an entitlement cannot be produced by the device or by the scan engine on its own.
How enrollment works
How enrollment turns a purchased seat into a signed device entitlement, and how replacements, sites and revocation are handled without over-consuming licenses.
Enroll the device
Start enrollment from the customer portal for the site the device belongs to. A device in pending enrollment does not consume a seat, so you can prepare hardware before committing a license.
Receive the signed entitlement
When enrollment completes, the operations portal issues a signed device entitlement license. Device entitlement is granted only from verified backend billing state, so an entitlement cannot be produced by the device or by the scan engine on its own.
The signed customer integration contract pins two operations for this flow: POST /api/v1/Devices/reserve-seat, then POST /api/v1/Devices/activate-device — both bearer-authenticated.
Replace or move a device
Deactivate the retired device and enroll the replacement so the released seat is reused instead of purchasing another. Moving a device between sites keeps the same subscription; the site assignment changes for administration and reporting.
Seat rules
Which device states consume a seat, how quantity changes apply, and how payment grace interacts with seats are the seat rules — owned by the billing guide. The portal's licensed-vs-in-use count is authoritative.