Web Consoles
Lists the Web Consoles in the project — pages Backstage builds and serves itself, so an operator can drive the show from a browser without Backstage's own interface. Opened from View > Web Consoles. The pages themselves are built in the Page Editor.
A console is only reachable while the REST server is running. Switch it on in Settings > Remote UI > Enable — one HTTP/REST server on port 8080 serves the browser Remote UI, the Web Consoles and the NDI input-slot API together.
Console list
|
Control |
Description |
Values / Range |
|---|---|---|
|
All |
Filter across every console, or pick one. |
Dropdown |
|
+ Add Web Console |
Creates a console. |
Button |
|
Web Console Options → Delete |
Removes it. |
Context menu |
With none in the project: No web consoles – use "+ Add Web Console" to create one.
Inspector
|
Setting |
Description |
Values / Range |
|---|---|---|
|
Name |
Name of the console. |
Text |
|
Serve path |
Path the page is served at on the web server, e.g. |
Path |
|
Serve on web server |
Hosts the page on the built-in web server, so it can be opened in a browser or the Web View window. Bound steppers and sequences stay in sync live. |
Checkbox |
|
Default page |
The page served at the base path. Empty means the first page. |
Page |
|
Minimum role |
Least privilege needed to open the page. Above Open to anyone the viewer must authenticate — via the BSM System Service, or the built-in users when standalone. |
Open to anyone / User / Operator / Administrator |
Serving is two switches, not one. A console with Serve on web server ticked but an empty Serve path is not reachable — an empty path disables serving on its own.
Related
Build and Serve Web Pages with the Web Console — building and serving a page
Page Editor — the editor the pages are built in
Enable and Configure the Show-Control Protocol — the machine-facing route to the same controls
Stepper — the locks that limit what a console operator may do