> For the complete documentation index, see [llms.txt](https://help.movin3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.movin3d.com/movin-tracin-stage/getting-started/the-workspace.md). # The workspace screen The workspace opens in a web browser on the control computer. On a kiosk machine, it opens automatically. The screen has four areas.
The workspace screen with its four areas marked

The four areas: 1 the top bar, 2 stage navigation, 3 the viewport, and 4 the inspector.

## 1 · Top bar — system status A status strip spans the top of the screen. * **System status** — an at-a-glance summary of the current state, shown as a single word: **SETUP** (setup is incomplete), **READY** (ready to start), **STANDBY** (previewing live data without broadcasting), **LIVE** (broadcasting), or **FAULT** (a problem needs attention). The line below shows what is preventing the system from becoming ready, or the elapsed time once the show is live. * **Status indicators** — **Sensors** (detected count; becomes `4/5` if one stops sending during a show), **Calibration** (Complete / None), **People** (people tracked right now), **OSC** (**Live** with the destination, or **Standby**), and **Rec** (elapsed clock while recording). An **LTC** indicator appears only while an external timecode source is locked. Hover over an indicator for details. * **Controls** — **GO LIVE** starts broadcasting, and becomes **END LIVE** while on air. **Restart** and **Stop pipeline** appear while the pipeline is running. The **⋯** menu holds **Server controls** (Reboot, Shutdown, and Restart GUI) and **Show welcome**. There is no separate start button — opening the **Settings** stage starts the system in preview. ## 2 · Stage navigation (left) Complete the three stages in order: **Calibration**, **Settings**, and **Live**. A completed stage shows a check mark; Calibration and Settings expand to show their sub-steps. A **NEXT** tag identifies the next required step. A stage that is not yet available is locked, and hovering over it shows the reason. **Calibration locks (🔒)** once the pipeline is running. ## 3 · Viewport (center) The live 3D point cloud, with the capture zones drawn over it. The **Display** control shows or hides the point cloud, the zones, and the mocap skeletons, and picks which point cloud is drawn. It only changes what you see — never what the show receives. A corner legend names which color belongs to which sensor and which zone. If a sensor stops sending during a show, an alert appears here — see [Running a show](/movin-tracin-stage/running-a-show/running-a-show.md#if-a-sensor-drops-out-mid-show). ## 4 · Inspector (right) A context panel that displays the controls and details for the selected item — a stage guide, the sensor list, the zones, the OSC output, and so on. ## First launch The first time you open the workspace, a welcome screen explains what the app does. Select **Got it** to dismiss it, then begin from the **Calibration** stage on the left. You can reopen it any time from the **⋯** menu → **Show welcome**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.movin3d.com/movin-tracin-stage/getting-started/the-workspace.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.