Console
The Infuse console includes an Infuse IoT area for operating the Infuse-IoT Cloud organisation linked to the active platform organisation.
Use the console for interactive fleet workflows: reviewing devices, creating boards and networks, dispatching commands, inspecting applications and releases, queueing device updates, and generating MQTT tokens. Use the API for provisioning, manufacturing automation, key derivation, bulk operations, and backend integrations.
Prerequisites
Before the Infuse IoT console pages can show resources:
- The active platform organisation must be linked to an Infuse-IoT Cloud organisation.
- Your user or API-key principal must have the permissions required for the action.
- Device, board, network, application, or release records must exist in the linked Infuse-IoT Cloud organisation.
If the console shows an empty or unavailable IoT area, first confirm the active organisation and its linked Infuse IoT organisation ID from Infuse IoT > API Access.
Console Areas
| Area | Use it for |
|---|---|
| Devices | Search organisation devices, inspect operational identity and state, open device details, update metadata, inspect KV entries, inspect logger state, view recent RPCs, and schedule application updates. |
| Commands | Dispatch an RPC manually using guided fields or raw JSON. Open RPC detail pages from device history or command responses. |
| Boards | View and create board profiles, including name, description, SoC, and metadata field rules. |
| Networks | View and create device networks using a numeric network ID and 32-byte base64 network key. |
| Applications | Browse Infuse IoT applications and releases, filter releases by version or board fields, and inspect release file metadata. |
| API Access | Copy the linked Infuse IoT organisation ID, manage Infuse IoT API key entry points, and generate MQTT tokens. |
Permissions
Infuse IoT console access is permission-gated. Common permissions include:
| Permission | Allows |
|---|---|
iot.applications.read | View IoT applications and releases. |
iot.devices.read | View IoT devices, state, metadata, KV entries, logger state, and related RPC context. |
iot.devices.update | Update device configuration such as metadata, KV updates, and application updates. |
iot.boards.read | View board definitions. |
iot.boards.create | Create board definitions. |
iot.networks.read | View networks. |
iot.networks.create | Create networks. |
iot.commands.execute | Dispatch commands to devices. |
iot.mqtt_tokens.create | Generate Infuse IoT MQTT access tokens. |
Organisation admins can inspect role permissions from Access > Roles. For general permission guidance, see Permissions.
When To Use The API Instead
The console is not intended to replace automated device onboarding. Keep these workflows in a trusted backend, manufacturing system, gateway, or service integration:
- creating or reconciling devices at scale,
- deriving shared secrets and device keys,
- handling provisioning material,
- issuing credentials automatically,
- syncing device registry records with another system,
- building customer-facing or partner-specific workflows.
For API-led onboarding, see Provisioning and Connect an IoT Device.