Desktop, fullscreen and kiosk mode: what changes?

Choose the mode deliberately

Desktop mode is suitable for setup and ordinary staff use. Fullscreen changes how the current window is displayed. Kiosk operation restricts access and is managed through supported launch/lock controls. Browser fullscreen alone does not prove the entire station is securely assigned to an application.

Prepare kiosk operation

1. Install and test the application in desktop mode first.
2. Configure the station administrator unlock method and intended application in Workstation.
3. Open through the supported kiosk action/launcher, then test switching/unlock and the expected absence of desktop-only close controls.
4. If reboot startup is required, configure it explicitly and test a restart. Installing an app by itself does not mean it should automatically take over the computer on every boot.
5. Verify the supported Linux session or Mac window setup and the real touchscreen/display layout.

Close and recover

End streams, recordings, races and other live work before maintenance. Use Close application only when available for the intended desktop session; kiosk instances can reject desktop close actions. If a process crashes, use the normal Workstation recovery path and diagnostics rather than opening repeated controller copies.

If the window is wrong

Record desktop/kiosk/fullscreen mode, operating system, display resolution, scaling and number of monitors. On Linux, verify X11/Xorg when the documented switching system requires it. A menu, title bar or close button can behave differently by launch mode; include that context in the report.