View managed connectors and request setup
Some connections need setup by Infodeck or your connection administrator. Existing records can appear in Settings → Integrations even when you cannot create or configure that provider on the page.
Open an existing connector to view its saved details. For managed network setup, AWS certificates or messaging credentials, contact your administrator or Infodeck Support. A saved connector is not proof that sensor readings or messages are arriving.
Before you begin
You need permission to view integrations in the correct workspace. Device access and deletion use separate permissions. If you cannot see the connector, ask your workspace administrator to check your access and its setup.
Which connections need assistance?
| Connector | What you can view | Setup outside this page |
|---|---|---|
| Infodeck LNS | Existing connector details and assigned device records | Infodeck provisions the managed network connection. |
| Infodeck Edge LNS | Existing connector details and assigned device records | Connection details are provisioned during Edge LNS appliance setup. |
| AWS IoT Core | Existing connector details and assigned device records | New connector setup and certificate provisioning are not available on this page. |
| Telegram bot, WhatsApp Cloud API, LINE Messaging API | Existing messaging connector details and available saved configuration summaries | New channel setup, credentials and access policy cannot be configured on this page. |
These providers are not choices in the standard Add connector setup form. For other providers, use the matching connector guide.
View an existing connector
- Open Settings → Integrations.
- Search for the connector name, or use IoT networks or Messaging to narrow the list.
- Select the connector to open its details.
- Review Administrator summary, when available. Sensitive configuration values are masked; this summary does not provide an editor for these providers.
For messaging connectors, the Messaging channel section explains that channel administration happens outside this page. Contact your administrator to confirm which messaging functions have been enabled for your workspace. An Active or onboarding status alone does not confirm that a particular message reached its recipient.
Check linked sensors
For Infodeck LNS, Infodeck Edge LNS and AWS IoT Core:
- Open the connector and find Devices.
- Review the Device, Identifier and Added columns.
- Select Load more if more records are available.
- To check reception, open the corresponding asset and inspect its recent readings using the sensor data guide.
The Devices list shows assigned records, not live telemetry. An empty list or an old reading needs investigation; neither identifies the cause by itself.
Users with deletion permission may see Delete device or Delete connector. Deleting a device permanently removes its record and telemetry routing. Connector deletion is blocked while devices remain or their count cannot be confirmed. Arrange changes with the connection administrator before removing anything.
Request setup or changes
Contact Infodeck Support with the connector type, whether it already exists, the sites and approximate device count involved, and what you want to achieve. For messaging, describe the intended channel and use case so the administrator can confirm availability. Keep connection credentials out of ordinary support messages.
Infodeck MQTT
If Add connector → Infodeck MQTT shows By project request, select Contact Infodeck to discuss the sites and device allowance. Some enabled workspaces have separate MQTT management controls. An allowance or saved connector alone does not mean device connection setup is complete.
Example: Check an existing managed sensor connection
A facilities manager wants to find a temperature sensor on an existing Infodeck LNS connection. Open that connector, find the sensor under Devices, then check its recent asset readings. If the device is listed but readings are missing, report the connector type and the observed problem to the connection administrator. Do not delete and recreate the connection to test it.