# Settings

> The station's own configuration on one scrolling page: appearance, branding, startup, localization, backups, crash reports, updates, and the legal texts.

Settings is the rail page for the station itself: how it looks, whose brand it wears, when it runs, how it writes dates and numbers, 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 {#the-left-index}

Four groups, nine rows, in this order: **GENERAL** (Appearance, Branding, Startup, Localization), **DATA** (Backups), **DIAGNOSTICS** (Crash reports) and **APPLICATION** (Updates, About, Legal).

The new-release mark on the status bar lands on Updates directly.

## In this area {#in-this-area}

| Page | What it covers |
| --- | --- |
| [Appearance](settings-appearance) | The theme, shared with the title bar's three keys, and the zoom of the desktop window. |
| [Branding](settings-branding) | The integrator's logo, icon and name, in place of the Ganter Lab brand in the title bar, the sign-in screen, the browser tab, the window, the tray and the report's default logo. |
| [Startup](settings-startup) | Start with Windows, what closing the window does, the tray icon and Exit. |
| [Localization](settings-localization) | Date, time and number formats, and every surface and file that reads them. |
| [Backups](settings-backups) | Configuration snapshots, the scheduled restore, the review notice and the run-history index rebuild. |
| [Crash reports](settings-crash-reports) | The automatic-send switch, what a report contains, the consent dialog and the debug commands. |
| [Updates](settings-updates) | Automatic updates, preview versions, checking, downloading and installing, and the status bar mark. |
| [About and Legal](settings-about) | The product text and version, and the Terms of Use and Desktop Privacy Policy with their acceptance state. |

## How the page saves {#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. 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 for about ten seconds unless it is dismissed or replaced first.

## What the stopped runtime does to this page {#what-the-stopped-runtime-does-to-this-page}

While the runtime is stopped, this page is not drawn at all: every screen except [Account](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 {#what-a-running-unit-locks}

A running unit holds the station's configuration, and the one part of this page that would change the plant under it is greyed with "Configuration is locked while a Unit is running.": Restore of a backup. Everything else on the page stays available while a unit runs.

## From a browser on another device {#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 two differences. The Desktop zoom row is not drawn (a browser has its own zoom). And two station-only commands stay drawn but greyed with "Available on the station's local desktop only.": Open folder on Backups, and Restart and update now on Updates.

## What the agent may touch {#what-the-agent-may-touch}

An agent connected through the [Agent](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 {#where-the-rest-lives}

The embedded OPC UA server, with its configuration and the applications it lets in, is a row of the Connector's [Servers](connector-servers) folder, beside the Modbus server; [remote access](remote-access), which opens the station's dashboards to other devices on the network, has a page of its own on the rail; and the certificates of the OPC UA equipment the station reads are approved on the [OPC UA driver's page](driver-opc-ua#equipment-access). Every protocol driver the package carries is listed in the catalog of the Connector's [Drivers](connector-drivers) folder; local users, roles and permissions are on the [Users](users) page; the agent endpoint, its port and its allowed areas are on the [Agent](agent) page; the Ganter account, the subscription and the feedback form are on the [Account](account) page; each dashboard's own settings are on [the dashboard's settings](view-settings).