A monitor bolted to a control-room wall or sitting in a lobby needs to show one thing, all the time, with nobody tending it. Kiosk mode is how a SCADA dashboard runs on that unattended screen: locked full-screen with no browser chrome, no way to navigate off the dashboard, often cycling through a set of screens on a timer, and signed in as a restricted read-only account. It is meant to survive a power cut, resist a curious passerby, and never time out and go blank, so the display just keeps showing the plant. This is the wall-display deployment pattern, distinct from an operator working interactively at a workstation.
Kiosk Mode in one line: Kiosk mode is a way of running a SCADA dashboard on an unattended display, such as a control-room wall monitor or a lobby screen, in a locked full-screen state with no browser controls, no navigation away from the dashboard, and often an auto-rotating set of screens. It uses a restricted read-only account and a session that never times out, and it is built to recover automatically after a reboot and to resist tampering, so the display keeps showing live data with no one attending it.
The visible essence of kiosk mode is that the dashboard fills the entire screen and nothing else is reachable. There is no address bar, no menus, no tabs, no visible operating-system controls, just the SCADA display edge to edge, so anyone looking at the screen sees only the plant data and has nothing to click that would take them elsewhere. This is deliberate: an unattended display should present exactly one thing and offer no controls, because every control is an opportunity for the screen to end up somewhere it should not be, whether by accident or by a passerby fiddling with it.
Behind that full-screen lock, navigation is constrained so the display cannot leave the dashboard. In an ordinary browser session a user can type a new address, follow a link, or back out to somewhere else, but a kiosk suppresses all of that, so there is no way to browse off the SCADA screen to another site or to the desktop. The display is pinned to its dashboard, and even the usual gestures and shortcuts that would exit full-screen or switch away are disabled or ignored. The screen has one job, showing the dashboard, and the kiosk lockdown removes every path by which it could be made to do anything else.
The account the kiosk runs under is restricted to match, read-only and low-privilege, because an unattended screen must never be a way to change the process. The kiosk session can view the dashboards it is meant to show and nothing more; it cannot acknowledge alarms, issue commands, or reach configuration, so even if someone did interact with the screen there is nothing to operate. This pairing of a locked interface with a powerless account is what makes an unattended display safe to leave in a public or semi-public spot: it can show the plant to anyone but cannot be used to touch the plant by anyone.
A single wall can usefully show more than one view over time, and screen rotation covers that by cycling the kiosk through a defined set of dashboards on a timer. A control room might rotate through an overview, then a compressor detail, then a tank-farm summary, each holding for a set interval before advancing, so one monitor tells several stories in turn without anyone switching it. The rotation is part of the kiosk's unattended behavior: it runs its loop indefinitely, so the wall stays informative and current across all the views in the cycle rather than being frozen on one.
For an unattended display, the ordinary idea of a session timeout is exactly wrong, so a kiosk session is built to never time out or lock. A normal login expires or locks the screen after a period of inactivity for security, but a kiosk has no user to re-authenticate and its whole purpose is to keep showing data continuously, so it stays signed in and displaying indefinitely. This is safe precisely because the account is read-only: there is no sensitive action to protect behind a timeout, so the session can remain up forever, which is what a display meant to run around the clock requires.
Because the display is unattended, it has to bring itself back after any interruption without a person present, and auto-recovery is what delivers that. After a power outage, a reboot, or a crash, the device should start up, sign into the kiosk account on its own, and return to the full-screen rotating dashboard with no human intervention, so a wall monitor that lost power overnight is showing the plant again by morning with nobody having touched it. This unattended resilience, auto-login on boot and automatic return to the locked dashboard, is essential, since the entire value of a kiosk is that it keeps running on its own, and a display that needs a person to restart it every time it hiccups is not really unattended at all.
Kiosk mode gives a distributed operation a permanent, glanceable window onto the field that anyone in the room can absorb without operating anything. A cloud SCADA platform such as Merobix can drive a wall monitor in kiosk mode showing a live fleet overview, so a control room, a shared office, or a shop floor always has the current state of the remote sites visible on the wall, updating on its own. Because the platform is served through the browser, standing up a kiosk is a matter of pointing an ordinary display at the dashboard in a locked full-screen session, without special hardware or a dedicated HMI appliance.
The read-only, tamper-resistant nature of the kiosk is what makes it appropriate for the places these displays actually go, which are often not locked control rooms. A screen in a lobby, a hallway, or a shared workspace is exposed to people who have no business operating the plant, so the fact that the kiosk can only display and never command means it can be placed in a semi-public spot without becoming a risk. It shows the fleet to everyone who passes and gives none of them any power over it, which is exactly the property a public-facing status wall needs.
Auto-recovery matters especially for these displays because they are meant to be forgotten, and a display you have to babysit defeats the purpose. Once a kiosk is set up on a wall monitor, it should run for months untouched, riding through the building's power blips and reboots by signing itself back in and returning to its rotating fleet view, so the wall is reliably showing live data every time anyone looks up. For a remote operation whose whole premise is watching sites from afar, a self-sustaining wall display that keeps the fleet visible without attention is a natural fit, and kiosk mode is the deployment pattern that makes an ordinary monitor into exactly that.
Because an unattended screen, especially one in a lobby or shared space, must never be a way to change the process. A read-only, low-privilege account can view the dashboards it is meant to show but cannot acknowledge alarms, issue commands, or reach configuration, so even if someone interacts with the screen there is nothing to operate. Pairing that powerless account with a locked full-screen interface is what makes the display safe to leave out in the open.
A normal login expires or locks after inactivity to protect sensitive actions, but a kiosk has no user to re-authenticate and its purpose is to keep showing data continuously around the clock. So a kiosk session is built to never time out, staying signed in and displaying indefinitely. This is safe precisely because the account is read-only, meaning there is no sensitive action behind a timeout to protect in the first place.
A properly configured kiosk recovers on its own. After a reboot or power loss the device starts up, auto-logs into the kiosk account, and returns to the full-screen, often auto-rotating dashboard with no human intervention, so a wall monitor that lost power overnight is showing the plant again by morning untouched. This unattended resilience is essential, since the whole value of a kiosk is that it keeps running by itself without someone restarting it.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.