Site Configuration
Edit site details, change operational status, and manage site settings.
After creating a site, you can update its details at any time. Open the site and go to Settings — the General section holds the edit form. You can also reach it from the Edit action in the sites-list actions menu.
Editable fields
The edit form includes the same fields as the creation form:
- Name — update the display name (max 255 characters)
- Alias — change the URL-friendly identifier (same validation rules as creation)
- Site Category — switch between any of the available site categories
- Operational Status — change to Active, Inactive, or Under Maintenance
- Location — update GPS coordinates and location label using search, map, or manual entry
- Commissioned Date — set or change the date the site became operational
Operational status
The operational status indicates whether a site is currently active and collecting data.
| Status | Description |
|---|---|
| Active | The site is operational. Edge gateways are expected to be running and streaming data. |
| Inactive | The site is not currently in use. This is informational — it does not stop edge gateways automatically. |
| Under Maintenance | The site is undergoing scheduled or unscheduled maintenance. |
The status is displayed as a badge on the sites list and across the site's pages.
Auto-publish configuration
The Auto-Publish Config setting controls whether changes to connectors and variable bindings are automatically published to edge deployments.
When auto-publish is enabled:
- Creating, updating, or deleting a variable binding triggers an automatic config publish
- Attaching or detaching a connector from an asset triggers an automatic config publish
- Changing a connector's protocol configuration triggers an automatic config publish
- The edge gateway picks up the new configuration on its next poll cycle (typically within 30 seconds)
When auto-publish is disabled:
- Changes to bindings and connectors are saved but not pushed to the edge
- The deployment shadow shows a Pending status indicating unpublished changes
- You must manually publish the configuration from the Gateways section
Auto-publish is useful during initial setup when you are frequently adding and adjusting bindings. For production sites, you may prefer to disable it and review changes before publishing.
The Settings page
A site's Settings page has three sections:
- General — the edit form described above (name, alias, category, status, location, commissioned date)
- Identifiers — the site's Site ID and Alias, with copy buttons, for use in API calls and support requests
- Danger Zone — permanently delete the site
Deleting a site
To delete a site, open its Settings page and use the Danger Zone, or open the actions menu (three-dot icon) on the sites list and select Delete. A confirmation dialog asks you to confirm the action.
Deleting a site permanently removes it along with all associated assets, variables, connectors, bindings, and deployment configurations. This action cannot be undone.