The access key the hub signs in to every terminal with. Create one "view and control" key on one terminal, then put the same key on the others with Add a key you already have on their Access keys page. The hub keeps it encrypted; it is never shown again.
Looks for IND700 Secure Screen on every address in the range. Nothing is changed on the terminals, and with the terminals' key set each one found is signed in to once to check the key and read its name. Adding a terminal trusts the certificate it showed just now.
One terminal per line: name, address, optionally followed by port, group. Paste it,
or open a CSV file. Terminals that do not answer now are added anyway, and trusted the first time they connect.
When drivers' codes (the stickers) work. Outside these hours a driver who scans is told when driver access is open; staff keys are never limited. A driver still watching when the hours end may finish, for the minutes set below, and is then disconnected. A code can be set to work at any time in its own Driver code panel.
A time range like 05:00-19:00; empty for closed all day; 00:00-24:00 for all day;
22:00-06:00 runs on into the next morning. The hub PC's clock and time zone are used.
While somebody watches, each terminal shows a small notice on its own screen so the person at it knows. Choose whom it names among the people watching through the hub; each key below can also be set to always or never show. A terminal can be set, in IND700 Secure Screen, not to let the hub leave anybody out.
Who can use this page. View watches, Control also uses the terminals, Admin also manages the hub. Limit a key to groups (for example Weighbridges) to show only those terminals. A key is shown once, when it is made.
Everybody watching a terminal through the hub, and everybody with this page open. Disconnect ends that connection and says who ended it; the person can connect again with their key. To keep somebody out, remove their key under Manage, Hub keys (or make a new driver code for a sticker).
Sign-ins, refused keys, who watched which terminal and for how long, and every change made here — kept on the hub PC as well, month by month.
A new address or port keeps this terminal's viewer link, its driver code (the sticker keeps working) and the certificate trusted for it. The hub connects to the new address straight away; if a different terminal answers there, it is refused until you accept its certificate.
A QR code to print and stick at . A driver scans it and has this terminal on the phone straight away, with no key to type. It opens this one terminal only.