Customizing Operator Layout and Views
The Operator Page has a ton of great information on it but it can easily be overwhelming and lose some of its usefulness in a regular game vs testing when you need all of the visibility. There are also controls and overrides that you may not want accessible in everyday use. To help with this you can create multiple Views that each have just what you need them to, you can also select one of these views to be the default one whenever the page is loaded and of course you can always click back over to see the full view of everything if needed.
UI path
- Open the Operator page.
- Click Add View.
- Choose which sections are visible.
- Reorder sections or items where supported.
- Hide controls, inputs, modules, outputs, variables, logic, or collections that staff do not need.
- Save the view.
- Set the default view if this should be the normal operator layout.
- Reload the Operator page and verify it opens correctly.
View settings
| Setting | What it does |
|---|---|
| View name | Saves a named layout preset |
| Default view | Opens this view automatically for operators |
| Card visibility | Shows or hides major cards such as Controls, Inputs, Outputs, Variables, Logic, and Collections |
| Item visibility | Shows or hides specific controls, inputs, modules, outputs, variables, or rules |
| Ordering | Moves important controls and cards higher in the page |
| Edit access | Requires admin or Simple UI password before changing views |
Recommended views
| View | Purpose |
|---|---|
| Staff | Only reset, hint, force solve, and essential status |
| Technician | Inputs, outputs, live events, controls, and diagnostics |
| Full | Everything visible for setup and debugging |
Do not depend on layout hiding for security. Use admin and Simple UI access controls for configuration protection.