Settings
The station's own configuration on one scrolling page: appearance, startup, localization, remote access, the embedded OPC UA server, backups, crash reports, updates, and the legal texts.
Settings is the rail page for the station itself: how it looks, when it runs, how it writes dates and numbers, whether other devices may open it, the embedded OPC UA server and who may talk to it, backups, crash reports, updates, and the two texts accepted at first use. The entry sits in the rail's foot group and is drawn only for a role that holds Change settings; the /settings route is guarded by the same permission, so a browser without it never reaches the page. The page is one long scroll with an "On this page" index on the left: each row of the index is a section, a click scrolls to it, and the index follows the section under the eye.
The left index
Six groups, thirteen rows, in this order: GENERAL (Appearance, Startup, Localization, Remote access), OPC UA SERVER (Status, Configuration, Client access), OPC UA EQUIPMENT (Equipment access), DATA (Backups), DIAGNOSTICS (Crash reports) and APPLICATION (Updates, About, Legal).
Several places in the app land on a row directly: the Review action of a certificate notification opens Client access or Equipment access on the certificate's row, the "Review certificate" button of a device waiting for its certificate on the Connector opens Equipment access, the new-release mark on the status bar opens Updates, and the "Open Settings" button of the Logic page's Server root opens Configuration.
In this area
| Page | What it covers |
|---|---|
| Appearance | The theme, shared with the title bar's three keys, and the zoom of the desktop window. |
| Startup | Start with Windows, what closing the window does, the tray icon and Exit. |
| Localization | Date, time and number formats, and every surface and file that reads them. |
| Remote access | Opening the station to other devices on the network, HTTPS, the port, the restart each change costs, and who may enter. |
| The embedded OPC UA server | The group overview, with Status, Configuration, Client access and Equipment access. |
| Backups | Configuration snapshots, the scheduled restore, the review notice and the run-history index rebuild. |
| Crash reports | The automatic-send switch, what a report contains, the consent dialog and the debug commands. |
| Updates | Automatic updates, preview versions, checking, downloading and installing, and the status bar mark. |
| About and Legal | The product text and version, and the Terms of Use and Desktop Privacy Policy with their acceptance state. |
How the page saves
Every control autosaves. A switch applies the moment it flips; a pick list the moment a value is chosen; a text field when you leave it or press Enter. Two rows deliberately ask before they act, because they restart something other screens depend on: the three settings of Remote access open a "Restart the web server?" dialog, and the fields of the OPC UA server's Configuration are a draft that only Apply & restart makes live. The outcome of every command on this page, success or refusal, lands in the status bar's action feed at the bottom of the window; a failure stays there until it is dismissed or replaced.
What the stopped runtime does to this page
While the runtime is stopped, this page is not drawn at all: every screen except Account is replaced by the paused notice, and the shell band above it carries the restart. Nothing on this page can be read or changed until the runtime is back, and everything comes back exactly as it was. The refusals listed against the individual controls below are what a command meets while the runtime is running and something else refuses it, never what the free-mode countdown does: when that runs out there is no page left to press anything on.
What a running unit locks
A running unit holds the station's configuration, and the parts of this page that would change the plant under it are greyed with "Configuration is locked while a Unit is running.": Start, Stop and Restart of the OPC UA server, its Configuration fields and Apply & restart, every certificate decision on Client access and Equipment access, and Restore of a backup. Everything else on the page stays available while a unit runs.
From a browser on another device
A browser signed in with a role holding Change settings sees this page as the station's window does, with three differences. The Desktop zoom row is not drawn (a browser has its own zoom). Three station-only commands stay drawn but greyed with "Available on the station's local desktop only.": Open folder on Backups, Restart and update now on Updates, and the Warnings meter's link to the Events window on Status. And certificate decisions are refused with "Client access can only be changed in the station's desktop app." (or the equipment wording): a browser may inspect both rosters, not change them.
What the agent may touch
An agent connected through the Agent page reads the display and lifecycle preferences (settings_read) and changes the formats and the theme (localization_set) while the Settings area is open there. It creates and lists backups behind the Backups area and schedules a restore behind that area's own opt-in, and it can never delete a backup. Nothing else on this page is reachable by an agent.
Where the rest lives
Protocol drivers are enabled and disabled on the Connector, on its Drivers registry; local users, roles and permissions are on the Users page; the agent endpoint, its port and its allowed areas are on the Agent page; the Ganter account, the subscription and the feedback form are on the Account page; each dashboard's own settings are on the dashboard's settings.