Provisioning Tokens
Generate tokens or USB configs to enroll devices at scale
Provisioning tokens provide automated device-to-account linking that eliminates manual pairing workflows during device deployment. This zero-touch enrollment architecture enables scaled rollouts where devices automatically configure themselves with account associations, network settings, and initial configuration parameters without requiring interactive setup.
Provisioning Token Architecture
Provisioning tokens function as pre-authorized enrollment credentials that devices consume during initialization to establish account membership and receive configuration parameters. Unlike manual pairing which requires interactive code entry for each device, provisioning tokens enable automated enrollment where devices self-configure using embedded credentials.
Each provisioning token encapsulates account linking credentials, optional device configuration parameters (tags, default playlists, network settings), and enrollment authorization. Tokens can be consumed by unlimited devices, making them suitable for bulk deployments where consistent configuration should apply across device cohorts.
Provisioning Delivery Mechanisms
USB-Based Provisioning
USB-based provisioning delivers token credentials via removable media during device initialization. Devices detect provisioning files on connected USB storage during boot and consume the embedded token credentials to complete enrollment automatically.
The provisioning file uses JSON format with standardized naming (telemetry_config.json) and must reside in the root directory of FAT32-formatted USB media. This approach suits field deployments where network connectivity may be unavailable during initial device setup, enabling offline enrollment that completes account linking once network connectivity establishes.
USB provisioning provides resilience for remote site installations where technical personnel may lack network configuration expertise. Installers simply connect power, displays, and insert the provisioning USB—the device handles all enrollment complexity automatically.
Programmatic Provisioning
Programmatic provisioning supports automated deployment workflows where devices receive token credentials through command-line parameters or configuration management systems. This approach suits enterprise environments with existing device management infrastructure or CI/CD-driven deployment pipelines.
Command-line provisioning accepts token values directly (--provisionToken) or references file paths containing token credentials (--provisionFile). This flexibility enables integration with configuration management systems, deployment automation scripts, or container orchestration platforms that supply credentials through environment injection.
Enrollment Behavior
Device enrollment proceeds automatically when provisioning credentials are detected during initialization. The device establishes network connectivity, validates the provisioning token with TelemetryOS infrastructure, receives account association and configuration parameters, and transitions to normal operational mode displaying assigned content.
Enrollment status appears on device displays during the provisioning process, with success confirmation indicating the device is fully enrolled and operational. Failed enrollments (due to invalid tokens, network issues, or account limitations) display error messages that guide troubleshooting.
Provisioning tokens remain valid indefinitely until explicitly revoked. Token revocation prevents new device enrollments using that token but does not affect devices already enrolled using the revoked credential.
Provisioning vs. Pairing
Provisioning suits scaled deployments (10+ devices) requiring consistent configuration, remote site installations, or offline enrollment capability. The automated workflow eliminates per-device interactive setup and enables non-technical installers to deploy devices successfully.
Pairing suits small deployments (1-10 devices), testing environments, or scenarios requiring immediate device-to-account linking with direct account access. For complete pairing documentation, see Pairing Devices.
Provisioning provides superior reliability for production deployments—devices cannot be "forgotten" or unlinked as easily as manually paired devices, and the consistent configuration reduces deployment variability.
Detailed provisioning procedures and configuration options cover advanced provisioning scenarios including network configuration, pre-configured tags, and deployment automation patterns.
Updated 13 days ago