Individual credentials
A compromised unit can be revoked without sharing a fleet key.
Integration at a glance
Separate privileges
Device, manufacturer, site and service authorities remain distinct.
Observed enforcement
A decision is not proof that an unreachable gateway has applied it.
Target supported hardware and an enabled site. Your application retains its own health and recovery responsibilities.
Credential separation
Use individual endpoint credentials from a dedicated device certificate hierarchy. Keep infrastructure credentials and gateway cloud-management credentials separate. The issuing service must protect its signing key; endpoint private keys remain local.
Verify the intended authentication server and trusted CA. Never repair a connection failure by disabling certificate verification or copying a working device’s private key.
Least privilege by role
Manufacturers manage their enrolled products and authorized fleet records. Businesses control individual network permissions and local capacity. Providers act through explicit customer delegation.
Service administration reviews production activation. That review does not substitute for a business’s local approval or grant a provider access to every customer.
Revocation and recovery
Revoke compromised credentials and applicable site access. Track router acknowledgement when disconnecting a live session. Renewal preserves the stable device identity and requires proof of the current credential private key.
Reporting tokens are tied to certificates and expire with them. Overlapping valid tokens survive routine renewal; device or credential revocation removes their authority. An active account and device are still required.
Keep a recovery path for expired credentials and trust updates. Recovery must not silently open the network, bypass site approval, or expose manufacturing automation credentials.
Data minimization
Expose only fleet and site information needed for the caller’s role. A device’s network permission does not create unrestricted manufacturer access to venue clients or traffic content.
Operational telemetry is not invoice-grade metering. Retention, commercial service terms, and privacy obligations must be established for production deployments.
Diagram and flow
- MANUFACTURER
Provision own products
Manage individual identities and authorized fleet records.
Enroll + review → Review service activation - FLEET ACCOUNT OWNER
Delegate scoped visibility
An authorized administrator explicitly grants and removes provider access.
Read-only grant → View delegated fleetsSeparate authority → Control site admission - SOLUTION PROVIDER
View delegated fleets
Support only assigned deployments with scoped read-only observations.
- HOTSPOTVU
Review service activation
Confirm supported platforms, sandbox limits and production readiness.
- LOCAL BUSINESS
Control site admission
Allow or deny individual devices and retain local capacity control.
Read the diagram description
- MANUFACTURER — Provision own products. Manage individual identities and authorized fleet records.Enroll + review → Review service activation.
- FLEET ACCOUNT OWNER — Delegate scoped visibility. An authorized administrator explicitly grants and removes provider access.Read-only grant → View delegated fleets.Separate authority → Control site admission.
- SOLUTION PROVIDER — View delegated fleets. Support only assigned deployments with scoped read-only observations.
- HOTSPOTVU — Review service activation. Confirm supported platforms, sandbox limits and production readiness.
- LOCAL BUSINESS — Control site admission. Allow or deny individual devices and retain local capacity control.