Console
The Infuse console includes an Infuse IoT area for operating the Infuse-IoT Cloud organisation linked to the active platform organisation.
The console calls Infuse IoT on your behalf using your signed-in session and your current IoT permissions in the active organisation; you do not need an API key to use it.
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. Organisations created in the Infuse Portal are linked automatically and use the same organisation ID in both.
- Your user or service account 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, find links to API-key setup, and generate MQTT tokens. Deprecated legacy Infuse IoT admin keys are also managed here until they are retired. |
Permissions
Infuse IoT console access is permission-gated. Common permissions include:
| Permission | Allows |
|---|---|
iot.applications.read | View IoT applications and releases. |
iot.applications.create | Create IoT applications, including releases and diffs beneath an existing application. |
iot.applications.update | Update IoT applications. |
iot.devices.read | View IoT devices, state, metadata, and recent RPC history and detail. |
iot.devices.update | Update device configuration such as metadata. |
iot.devices.control | Dispatch RPCs, access device keys, and update or cancel device KV, logging, and application operations. |
iot.boards.read | View board definitions. |
iot.boards.create | Create board definitions. |
iot.boards.update | Update board definitions. |
iot.networks.read | View networks. |
iot.networks.create | Create networks. |
iot.networks.update | Update networks. |
iot.mqtt_tokens.create | Generate Infuse IoT MQTT access tokens. |
Device control is separate from device reads and updates. A user with read access can review a device's RPC history, but the console disables command dispatch and KV or application actions unless they also have iot.devices.control.
Organisation admins can inspect role permissions from Access management > Roles. Infuse provides shared templates for common jobs: IoT Viewer, Device Operator, Device Controller, and IoT Admin. Assign a compatible template directly, assign it through a group, or clone it to create an organisation-owned custom role. See Member Roles for what each template includes.
Open the user under Access management > Members, or the machine identity under Access management > Service accounts, when you need to trace a current IoT permission to its direct role, group-inherited role, or direct grant. For general permission guidance, see Permissions and Resource Limits.
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.