A data lab is where your data and pipelines run. The Space is the control plane that manages your labs: their access, configuration, version, start/stop and backups. When you open a lab from the Space, you land on its detail page — a set of tabs whose landing tab is the dashboard. This page describes how to open a lab, what the dashboard shows, and the tabs available on a lab.
Opening a lab
Open a lab from the Labs section of the Space. Selecting a lab opens its detail page. At the top of the page a header shows the lab name alongside a status chip that reflects the lab's live status, and below it the row of tabs. The dashboard tab is selected by default.
The lab's landing view depends on your lab role. Anyone with access to a lab (as user or owner) can do anything inside the lab, but only an owner can configure, start, stop and grant access to it. Some controls and tabs described below appear only for owners (or, for one tab, space admins).
The dashboard
The dashboard is the lab's landing tab. It gathers the essential information and controls for the lab into a few sections:
- Lab detail card — identity and quick actions for the lab (see below).
- Server information card — shown only for cloud labs, next to the lab detail card.
- Users list — the people who have access to the lab and their roles.
- Folders list — the folders connected to the lab.
Lab detail card
This card carries the lab's identity. It shows the lab name (owners can rename it in place by editing the title), the lab type, and, for a lab hosted on a server, the lab URL (a link that opens the lab in a new tab). Depending on the lab it may also show the region, the billing mode, the desktop platform, and a note when the lab is a free data lab. A card menu (the more icon) gives access to codelab info and the list of installed bricks; for a desktop lab it also offers update and delete actions.
The card footer holds the access actions for a server lab: a button to log in to the lab (when it is HTTP-accessible), and — for cloud labs, if you are an owner — the start / stop control.
Starting and stopping a lab
The start / stop control is a single toggle button whose state follows the lab's server status. Only a lab owner can start or stop a cloud lab.
- When the lab is not running, the button reads Start lab. Pressing it opens a confirmation dialog, then launches the lab. It is disabled while an action is already in progress or when the lab has no server configured.
- When the lab is running, the button reads Stop lab. Pressing it opens a stop dialog; if backup is enabled for the lab, the dialog offers a checkbox to back the lab up as part of stopping it.
After a start or stop, a message confirms the outcome — the lab is starting, stopping, started or stopped — and the status chip in the header updates accordingly.
Lab global info
A Lab global info card gives a detailed, at-a-glance health check of the lab. It lists a series of OK / not-OK indicators — for a cloud lab: whether the server instance, the server volume and the DNS are configured; and for every lab: whether the lab manager is running and whether the lab itself is running. It also shows the lab's current task and surfaces any warnings or server errors.
Two buttons sit in the card header: Codelab info and Refresh status, which forces an immediate refresh of the lab's status. The card also offers the log in and start / stop controls.
Lab tabs
The lab detail page is organised into tabs. Which tabs appear depends on the lab type and on your role:
