Connector Configuration
Edit connectors, manage asset attachments, and override inherited connectors.
After creating a connector, you can update its settings and manage which assets it is attached to. Attachments can be managed from either the asset side or the connector side.
Editing a connector
Navigate to the connector detail page and click Edit. The following fields can be updated:
| Field | Editable | Notes |
|---|---|---|
| Name | Yes | Up to 255 characters, unique within site |
| Endpoint | Yes | Connection address |
| Protocol Config | Yes | Protocol-specific settings (security, ports, etc.) |
| Protocol | No | Cannot be changed after creation |
| Alias | No | Cannot be changed after creation |
Updating the endpoint or protocol configuration increments the site's configuration version. If auto-publish is enabled, the updated configuration is automatically pushed to edge deployments.
Attaching connectors to assets
There are two ways to attach a connector to assets: from the asset detail page (one connector at a time) or from the connector detail page (multiple assets at once).
From the asset detail page
To attach a connector from the asset side:
- Open the asset detail page and go to the Connectors tab
- Click Attach Connector
- Select a connector from the dropdown (only connectors not already attached to this asset are shown)
- Click Attach
The connector is attached directly to the selected asset and inherited by all its descendants. The confirmation message shows how many attachments were created (direct + inherited).
Attaching a connector to an asset also attaches it to all descendant assets automatically. You do not need to attach the same connector to each child asset individually.
From the connector detail page
To attach a connector to multiple assets at once:
- Open the connector detail page and go to the Assets tab
- Click Attach to Assets
- In the dialog, a tree view of all assets in the site is displayed. Select the assets you want to attach the connector to by checking their checkboxes.
- The tree supports expanding and collapsing branches to navigate the asset hierarchy
- Assets that already have this connector attached (either directly or through inheritance) are shown as disabled with an Attached badge and cannot be selected again
- Parent checkboxes show an indeterminate state when only some children are selected
- Review the summary at the bottom of the dialog. It shows:
- The number of direct attachments that will be created (one per selected asset)
- The approximate number of descendants that will inherit the connector automatically
- Click Attach to confirm
The platform processes attachments sequentially and displays a progress indicator. If an individual attachment fails (for example, due to a conflict), the operation continues with the remaining assets. A summary of successes and failures is shown when the operation completes.
The bulk attach workflow is especially useful when a single data source serves many assets across different branches of the hierarchy. Instead of navigating to each asset individually, you can attach the connector to all of them in one operation.
Viewing attached assets from a connector
The Assets tab on the connector detail page shows all assets that have this connector attached, displayed as a table:
| Column | Description |
|---|---|
| Asset | Name (clickable link to asset detail) |
| Path | Location in the asset hierarchy (for example, "Production Line A > CNC Machine 001") |
| Type | "Direct" (explicitly attached) or "Inherited" (from parent) |
| Actions | Detach button (direct attachments only) |
Direct attachments are shown with a blue Direct badge. Inherited attachments are shown with a faded Inherited badge and an arrow icon indicating the attachment was propagated from a parent asset.
Viewing attached connectors on an asset
The Connectors tab on an asset detail page shows all connectors attached to that asset:
| Column | Description |
|---|---|
| Connector | Name (clickable link to connector detail) |
| Protocol | Protocol badge (color-coded by type) |
| Type | "Direct" (explicitly attached) or "Inherited" (from parent) |
| Endpoint | Connection address |
| Actions | Detach button (direct only), Override option (inherited only) |
Inherited connectors are visually distinct (reduced opacity) and cannot be detached from the child — you must detach from the parent asset where the direct attachment exists. However, inherited connectors can be overridden with a different connector.
Detaching a connector
You can detach a connector from either the asset side or the connector side. In both cases, only direct attachments can be detached. Inherited attachments must be detached from the parent asset where the direct attachment exists.
From the asset detail page
- Open the asset's Connectors tab
- Click Detach on the connector row (only available for direct attachments)
- Confirm the action
From the connector detail page
- Open the connector's Assets tab
- Click Detach on the asset row (only available for direct attachments)
- Confirm the action
In both cases, detaching removes the direct attachment and all inherited attachments from descendant assets. If a descendant has its own direct attachment to the same connector, that direct attachment is preserved.
Detaching a connector removes inherited attachments from all descendant assets. Any variable bindings on those assets that reference this connector will no longer receive data.
Overriding an inherited connector
When an asset inherits a connector from its parent, you can replace it with a different connector. This is useful when a specific asset or branch of the hierarchy connects to a different data source than the rest.
To override an inherited connector:
- Open the asset's Connectors tab
- Find the inherited connector you want to replace
- Click Override on the inherited connector row
- Select the replacement connector from the dropdown
- Review the impact preview, which shows:
- The assets that will be affected (the current asset and its descendants)
- Any variable bindings that will be deleted because they reference the old connector
- Any variables that will become unbound as a result
- If bindings will be deleted, confirm that you want to proceed
- Click Override to apply the change
The override operation is transactional — the old inherited connector is removed and the new connector is attached as a direct attachment on the target asset in a single operation. If anything fails, no changes are made.
After the override, the new connector is inherited by all descendants of the target asset, replacing the old inherited connector throughout that branch.
To revert an override, detach the direct attachment of the replacement connector. The asset will then re-inherit the original connector from its parent.
Attachment types
| Type | Badge | Description |
|---|---|---|
| Direct | Link icon, blue "Direct" badge | Explicitly attached to this specific asset |
| Inherited | Arrow-down icon, faded "Inherited" badge | Propagated from a parent asset higher in the hierarchy |
For a detailed explanation of how inheritance works, see Connector inheritance.
Configuration changes and auto-publish
Changes to a connector's configuration can trigger automatic re-publishing of edge deployment configs when auto-publish is enabled on the site. This includes:
- Updating the connector endpoint
- Changing protocol configuration (security settings, subscription parameters, etc.)
- Attaching or detaching the connector from assets
- Overriding an inherited connector