Skip to content

Workspace and panels

Terminal’s panels can be docked, resized, grouped, and opened through the Panels menu or ⌘K command palette. Which panels exist depends on the Mainline Packages this Mainframe has installed: Tracks comes with Air Picture, Missions and Control with Drones, Chat with Comms and Voice with Comms’ voice module; Weather, Analyst and Assistant need their modules enabled. A panel, menu item or palette entry of a package that is not installed is not shown at all. The palette lists every action Terminal can perform, with its key where one is bound; unavailable actions stay listed with the reason. Shared layouts provide starting points; save your own after arranging the panels you use regularly (see Layouts).

The menus come first. TERMINAL, behind the Terminal mark, holds the selection groups A–D and Clear Selection, Terminal Settings…, the Mainframe you are connected to (Connected to SAB) with Connect to Mainframe… and Mainframe Settings…, and who you are signed in as with Profile… and Sign Out. Panels opens any panel. Layout holds the shared layouts (one click applies one; the check marks the last one applied), Undo and Redo, the Timeline Bar, Hide Tabs, Lock Layout and Command Rail switches (see Command Rail), Video Overlays, then Close All Panels, New Window, Save Layout As… and Manage Layouts…. Plan draws new markings and missions and opens Missions and Markings.

After the menus comes the selection: the selection group chips when more than one group is in use, then the selection menu, which shows the focused aircraft (hover it for battery, altitude, speed, link, satellites and heading), the focused object, or No selection. Click it to pick one of the aircraft online now, the quick way to select one before taking control; a role that arranges panels also finds Selection there, which opens the Selection panel. Then comes what this window holds: CTRL YOU · V03 for a control lease (CTRL <name> when someone else holds the selected aircraft), KEYS ▸ V03 while the flight keys are armed, VOICE · Team Alfa for the voice rooms you are in (see Voice).

On the right: PENDING n airframes waiting for approval (opens Assets), only when there are any; the unacknowledged alert count (opens Alerts); the UI frame rate, amber under 30 and red while the air picture’s age is past 2 s (below), which opens the UI performance popover (with two or more videos playing, the browser paces the whole page to their frame rate — about 30 FPS with 30 fps cameras, 15 with 12 fps ones — and the popover says so instead of turning amber); and the clock. The page ends with the timeline bar.

On a narrow window (a top bar under 768 px) the bar keeps to one line: the Terminal mark without the word, the layouts as one dropdown named after the active layout, the selection as its dot and callsign, and no frame rate or live clock (a link warning still shows). In replay it shows only the transport and LIVE.

A layout is shared with everyone on the Mainframe. Choosing one in the Layout menu replaces the panels on screen; the check mark stays on it while you move, add and close panels, and a reload keeps your arrangement as you left it.

A layout starts as one arrangement for any window size. Configurations add arrangements for narrower ranges of window size, each with a width bound (Width < 1400, Width > 2000 or any width) and a height bound. The configuration that fits the window best is used: the one that narrows more sides, then the one whose bounds lie closest to the window’s size. When a resize crosses into another configuration’s range, that configuration replaces the arrangement; resizing within one range never does. A window opened at a size that falls under another configuration than the one it closed with switches too.

Save Layout As… offers three choices:

Choice Does
New Layout Saves the panels on screen under a new name; a name another layout has is refused
New Configuration Pick a layout, name the configuration, and narrow the window size it is for
Update Existing Pick a layout, then one of its configurations: the panels on screen replace its arrangement

Manage Layouts… lists every layout with its configurations below it. Apply, Rename… and Delete Layout… act on a layout (a deletion asks first and cannot be undone); a configuration’s menu renames it and changes its sizes, or deletes it. The first configuration is for any size: it can be renamed but not resized or deleted. Each layout also sets four view options when you change to it: Timeline Bar, Hide Tabs, Lock Layout and Command Rail, each Preserve (leave it as it is), On or Off.

A browser with no arrangement of its own starts from the Mainframe’s default layout (Mainframe Settings → Configuration → Workspace). A role can name a layout (Mainframe Settings → Roles): it is applied when one of its members signs in, never on a reload. Saving, renaming and deleting layouts needs a role that writes layouts and customizes; a role applies the layouts it uses (layouts.use, see Access). Alt+1 to Alt+5 switch to the first five layouts of the menu.

Everyone starts in Fixed Layouts. The top bar shows TERMINAL, then the layouts the role uses as a row of buttons (Alt+1 to Alt+5 switch to the first five), then the selection. There are no Panels, Layout or Plan menus. A role with layouts.customize leaves with the top bar’s Unlock Layouts button and returns with Layout → Enter Fixed Layouts; this browser remembers the choice. Roles without it (the starting operator and observer roles) stay fixed.

The layout’s panels stay where it put them: no + to add a panel, no close button, no dragging or floating, no Close or Duplicate on a tab (Maximize remains). The sashes still resize unless Lock Layout is on. Lock Layout on its own (while customizing) freezes the sashes and drags and also keeps every panel open: no close button on a tab, and Close is disabled (Layout locked). Nothing opens a new panel: whatever shows its result in a panel the layout lacks is left out of the palette, the menus and the toolbars — Show on Map without a Map, the Alerts chip without Alerts, PENDING without Assets, Open Chat and every Send to Chat without a Chat panel (with one, it switches that panel to the group). The same holds for the Open button on a notification (a capture, a clip, a chat message, a new pin), View capture in a timeline marker, a double-click on an Analyst result, Open Missions in Control, and Ask the Assistant in the palette. An aircraft’s Video, Telemetry, Control and Analyst buttons (its menus, the Selection panel, a mention, a double-click on the map) appear only for panels the layout holds, and switch that panel to the aircraft instead of opening another. Double-clicking a Video Wall tile turns the wall itself into that feed’s Video panel; Back to Wall, before the feed chip, returns to the grid. A view option the layout sets On or Off holds the switch there; one left at Preserve can be flipped as usual (t, the palette).

A browser in Fixed Layouts always shows one of the role’s layouts: the role’s layout at sign-in, the Mainframe’s default, or the first one.

Layout → Command Rail (also in the palette) replaces the top bar with rails of 48 px icon tiles at the window’s edges, for a touch screen. With it on every control is half again as large — buttons, menu rows, tabs, list rows — while maps, video and readouts keep their size. The switch belongs to this browser; a layout can set it like the other view options, and a role whose layout sets it On starts in rails at sign-in. Each window reads the switch when it opens: a window opened with New Window follows it, and flipping it in one window changes the others when they reload. The first time a finger touches Terminal with the rails off, a toast offers Use Command Rail, once per device.

A tile is an action. It has no caption: hover it with a mouse, or hold it with a finger, to name it. Two tiles are always there:

  • Terminal, the Terminal mark, opens the Terminal menu and, while customizing, Panels, Layout and Plan as submenus, then Command Palette, Edit Rails… and Command Rail (the way back to the top bar; in Fixed Layouts too, unless the layout sets the option). The UI frame rate sits at its foot; the tile shows an amber or red dot when the frame-rate chip would have.
  • Clock shows HH:MM over LIVE, or the amber time behind live in replay (−5:12), SYNC, NO LINK or ARCHIVE. It opens the full time with rewind 1, 5 and 15 minutes, Jump to Time…, Send Time to Chat and Copy Time; in replay, the transport, the rate and LIVE.

The default rail, on the left, also holds the selection (its menu of aircraft online and the selection groups), the alert count, Talk in Every Room, the layouts (one tap opens them, one more applies one), Follow Active Selection, Capture Frame, Pin at Camera Aim and the palette. Status tiles carry what the top bar showed: the control chip, the voice room and PENDING. Tiles that do not fit collect under a … tile.

Rails belong to the layout: everyone on a layout sees its rails, and a layout without rails of its own shows the default rail. Save Layout As… copies the active layout’s rails. Edit Rails… (in the Terminal tile’s menu, while customizing) edits them in place: + at the end of a group adds a tile (any action or entry: a panel, a layout, an aircraft, a room), a tile’s menu changes its icon to any Lucide icon, moves it or removes it, the bar switches the Left, Top, Right and Bottom rails on and off, Copy Rails From takes another layout’s rails and Reset to Default goes back to the default rail. Done saves for everyone who uses the layout, with an Undo in the toast; Cancel drops the edit. A right-click or a hold on a tile opens its menu outside the editor too: its name and key, Customize… and Delete (the Terminal and Clock tiles cannot be deleted). In Fixed Layouts the rails are the layout’s as they are, without the editor, and a tile whose action the layout leaves out does not show. A tile whose action belongs to a package this Mainframe has not installed (Talk in Every Room without Comms, the control chip or PENDING without Drones) stays in the layout but does not show; in the editor it is dimmed and named Not on this Mainframe, with only Remove in its menu, and + does not offer such actions.

Selection groups A–D let separate groups of panels follow different aircraft or entity sets. Use the panel’s toolbar chip to follow a selection group or pin a suitable panel to one aircraft. Assets, charts, map selection, and the video wall can work with more than one selected aircraft.

Click normally to replace a selection. Modifier-assisted selection and Assets range selection build a set. On the map, shift-drag selects a region. Use the visible selection controls when working on a device without a keyboard.

Everything drawn on the map is selectable: aircraft, radars, controllers, sites, detections, markings, routes and capture glyphs. A click selects, a double-click opens the object’s natural panel or editor, and a selected object shows a ring in its channel’s colour. The Selection panel describes whatever is selected — what it is, which module provides it, its key facts and the actions available on it. Notes on a capture or a marking are in the Captures and Markings panels.

The Panels menu, and the dock’s + menu, list the panels in five groups, the same as the tables below.

Panel What it helps you do
Map See aircraft, detections, sensors, markings, routes, and the ground each camera sees (the picture’s corners on the ground, capped at 3 km); draw and edit markings and routes in place; right-click anything, or the ground, to send it to a chat group
Assets Browse bases, flights, aircraft, phones, sensors and effectors (each launcher with its interceptors under it, its State 4/4 ready); compare state, battery and assignment in columns; select aircraft and issue available commands; + New adds a base, a flight or an aircraft source; a row’s menu sends the aircraft to a chat group
Missions Create and edit missions, inspect assignments, and review coverage
Markings List everything drawn on the map by kind, show or hide a kind, edit or restyle a marking, leave notes on it, and send it to a chat group from its row menu

The layers popover (the stack icon on the map) starts with the basemap, then switches each layer in three sections:

  • General — Paths, Missions, Markings, Labels, Wind, 3D View (the map tilted, tracks at their heights on stalks, zones as volumes; H toggles it too).
  • Drone — Camera FOV, Detections, Captures, Coverage age.
  • Air Picture — Air tracks, Prediction cones (off by default; see Threat), Pending tracks, Plots, Raw picture (every sensor’s own plots and tracks instead of the fused picture; Shift+R toggles it too), Sensor coverage (in 3D also the sensors’ coverage domes; on the 2D map a radar’s or camera’s coverage is cut where the terrain hides a drone 50 m above the ground from it — hills, and the forest canopy around a low mast — once fusion has the terrain model, else its full sector), Cameras (each pan-tilt-zoom camera’s field of view as a wedge on the ground, as long as it can still recognise a small drone at that zoom; stronger while it looks at a track), Bearings (each RF direction finder’s lines of bearing of the last 5 seconds, fading; the selected track’s own drawn wider) and Effectors (each launcher and jammer as its symbol with its reach — a launcher’s ring between its minimum and maximum range, a jammer’s sector, brighter while it transmits — coloured by readiness: blue ready, amber low, grey out or reloading; and the engagements, see Engage a threat).

Two layers hold a control under their switch:

  • Paths draws every aircraft’s and phone’s path over the chosen window, 5 minutes to 6 hours (map.trailWindow). Paths fade to half opacity towards the window’s edge; the selected aircraft’s path is wider on a dark halo. Each aircraft draws in its own colour: a fixed pick per airframe until you set Path color in Identify airframe (phones: Configure phone).
  • Coverage age darkens ground nobody has looked at (25 % brightness), tints ground in a camera now green, and fades seen ground from full brightness to half at the fade horizon (Mainframe Settings → Configuration → Coverage). The slider under the switch sets how strongly the fog applies (map.coverageOpacity). In Replay the map shows the snapshot Mainframe stored nearest the playhead (one a minute, kept for the bulk horizon under Configuration → Retention) and follows the replay from there.

Tracks and Selection show each fused track’s age: how long ago the fusion module received the newest measurement behind it, against Mainframe’s clock, in tenths of a second (0.8 s) up to ten seconds. The Tracks header ends with the picture’s 95th-percentile age (age p95 0.9 s); each row’s Age column and the selected track’s AGE 0.8 s in Selection read the same figure. It turns amber past 0.6 s and red past 2 s, the limit for a displayed position. The frame rate’s popover lists Track age p95 for the tracks the map last drew, and Mainframe’s clock offset and round trip; the frame-rate chip turns red while that p95 is past 2 s. In Replay the age counts to the playhead and carries no colour.

A fused track is on the map from its sensor’s first report, before the fusion module has confirmed it. Until then it is pending: its symbol has the dashed (anticipated) frame, it is drawn faded, and its label ends in P. It becomes confirmed — solid frame, full opacity — when one of the confirmation rules passes: a second report from a fast radar (one that revisits at least once a second), a slower radar’s score, a trusted tracker’s confirmed track, two independent sensors, a cooperative identity (ADS-B, Remote ID) or an operator’s report. A confirmed track stays confirmed while it lives. A pending track that never gets its second report simply leaves the picture. (With the Conservative rules below, none of this is shown: a track appears only once confirmed.)

  • Tracks has a Pending toggle (on by default) and an Ex column (P amber, C); sorting by it puts the pending tracks first.
  • Selection shows a PENDING chip and an Existence line: Pending · 1 report, or Confirmed 0.9 s after first report · 2 reports (how it was confirmed, in words).
  • The Pending tracks layer (Air Picture section) hides pending tracks from the map.
  • A pending track inside a zone raises a warning alarm after the zone dwell (0.5 s); when the track confirms, the same alarm turns critical in place. A Tracks row’s zone badge is amber for a warning, red for a critical alarm.
  • The rules live in Mainframe Settings → Fusion → Confirmation; each sensor type can carry its own report count. Recipients (CAT 062, CoT) get pending tracks as tentative or not at all — each recipient’s Pending tracks switch.

Mainframe Settings → Fusion → Confirmation → Track confirmation picks one of two sets of rules; each rule below it stays editable (an edited set reads as neither).

Fast (MOGS ≤ 2 s), the default Conservative (before AP4)
A single radar’s track confirms second report from a fast radar (revisit ≤ 1.05 s; third in a clutter cell), else score 3.5 score 3.5 from every radar: six straight reports, twelve where tracks keep dying (a clutter cell)
Trusted trackers first confirmed report confirms off
Pending tracks on the map, in Tracks, to recipients, warn in zones held back: nothing sees a track until it confirms
A confirmed track stays confirmed while it lives goes back to pending when no rule holds and every contributor’s score falls below zero (a lucky echo or bird track)
Two sensors, ADS-B / Remote ID, a person’s report confirm at once confirm at once

Conservative writes fastRevisitS 0, trustedTracker off, publishPending off and keepConfirmed off; Fast removes them again. Conservative is the calmer picture over birds and ground clutter; a lone fast radar’s drone then takes about 1.5 s (4 Hz) to 6 s (1 Hz) to appear instead of 0.25–1 s, so it does not meet MOGS’ 2-second rule on slower radars. Changing it reloads the fusion module’s rules at once; tracks already confirmed stay so under Fast.

The map paints a new picture as it arrives (at most once a frame), so a fast radar’s track moves up to ten times a second. Hovering a track shows how far ahead its position is reckoned (· reckoned +0.2 s).

In Replay the air picture is the playhead’s, never live (existence is stored with the track’s position once a second, so a track confirmed between two stored samples reads pending until the next one): Tracks lists the tracks of that moment (its counts and Sensor filter too; quarantine counts and discovered devices are live-only and hidden), the map’s track symbols stand where they were with 30 s trails read from the stored history, Selection and its History stop at the playhead, and the Raw picture, the Plots layer and fusion lines show the plots the fusion module decodes from its raw log for that minute. Where nothing was recorded — before the raw log began, or with no sensor then — the Raw legend reads RAW · NOT RECORDED AT THIS TIME and nothing is drawn; RAW · UNAVAILABLE means the raw log could not be read. Go live restores the live picture.

One group of buttons at the bottom right of the map: + and − zoom this map, and the compass shows where north is. Click the compass to reset the view: north-up, flat on the flat map and at the 3D picture’s tilt in 3D. Drag it sideways to turn the map and up or down to tilt it; Alt-drag on the map does the same. The 3D switch is in the layers popover. The group hides with the tab strips under Hide Tabs and comes back while you peek.

With 3D View on, each air track’s symbol stands at its height on a stalk from the ground, with its name and height under it, and its recent path at height behind it; click a symbol to select the track. Your own drones, phones, cameras and bases are marks in the same picture, each a friendly symbol (drones at their height above the ground, the rest on the ground) with its callsign, in place of its flat-map marker; click one to select it. On Mapbox builds every mark is its APP-6 symbol; on MapLibre builds it is a disc in its frame colour. Plots with a measured height (a 3D radar’s) stand at it; plots without one (a 2D radar’s) stay on the ground, under the track’s stalk. Tracks move smoothly between their reports, on the flat map too: each is drawn where its last report’s speed and heading put it, for at most a few seconds, and a new report’s correction blends in instead of jumping. A paused Replay shows every track exactly where its report says. Terminal Settings → General → Map → Smooth track motion (on by default) turns the gliding off: tracks then jump to each report.

Fusion scores every track’s threat from 0 to 100 once a second: its class, identity, how soon its predicted path enters a zone (times the zone’s priority), its behaviour (approaching, loitering, passing), its height, speed and whether it is confirmed. The score’s band is its level — high (red), medium (amber), low — and the live tracks are ranked, operator-set levels first.

  • Tracks sorts by Threat, highest first, by default (click Track for names); the column shows the score in its level’s colour, and the header counts 2 high · 4 medium.
  • The track’s block in Selection has a Threat section: High 82 · unidentified · quad · 40 s to VNO, its rank, and the zones the prediction reaches (VNO in 40 s, counting down; may enter when only its uncertainty touches the zone). Set Threat… sets your own level with an optional reason; it replaces fusion’s until Clear, and shows who set it and when.
  • On the map the selected tracks, and tracks with an open zone or approaching alert, draw a prediction cone instead of their 15 s leader: the predicted path widened by twice its uncertainty, fading with the horizon, with ticks at 10, 30 and 60 s (2D only). The cones are their own layer, Prediction cones (Air Picture section), off by default; with it off every track keeps its leader.
  • A track whose path enters a zone within the next minute raises an approaching alert: Drone enters VNO with ETA 0:42 counting down in Alerts; it resolves at the entry, when the zone alarm takes over. A zone alarm’s severity follows the threat: critical for a high or medium threat, warning for a low one (after the level has held 3 s).
  • In Replay the sort, the cone and the Threat section read the cursor; Set Threat… is unavailable. Mainframe Settings → Fusion → Threat sets the factors’ weights, the band edges and how far ahead zone entries count; a zone’s Priority (zone settings) weighs its entries.

Set Identity, Set Class, Set Threat, Mark False Alarm, Merge With and Split open as a small popover where you asked for them: under the Selection panel’s button, at the row in Tracks, at the clicked point on the map, or — from the palette — at the track’s row or its mark on the map. Merge With lists the other selected track first, then the five nearest; Split lists the track’s contributors. Each row’s button is the choice; Esc closes the popover.

As soon as a track is confirmed, its block in Selection shows an Engagement section with the effectors that can reach it, ready ones first, then the quickest: Effectors · IXL-4 VNO · intercept · ETA 35 s · Pk 0.86 · class pending. Engage With… is available at once. Each effector says why it is not recommended yet: class pending (the track is not classified), not for balloon (it does not engage the track’s class), no emitter heard (a jammer, with nothing jammable heard from the track: an FPV on a fibre radiates nothing) or not ready. Waiting for a class is your choice.

When fusion rates the track medium or higher and an effector engages its class, that effector is the recommendation: the row reads Recommended · IXL-4 VNO · intercept · ETA 35 s · Pk 0.86 · +1, and Tracks marks the row ENG. A balloon, a bird or an aircraft is never recommended (its list flags every effector). The recommendation stays 15 s after the threat dips below medium.

  • Engage With… (the section’s button, the track’s right-click menu, the palette) opens a popover with the list: each effector’s time to effect, Pk, why and readiness, Recommended or its flags. An effector that is not ready cannot be chosen. Engage on a row asks once (Engage T12 with IXL-4 VNO? — Launches an interceptor · ETA 35 s · Pk 0.86, and Not recommended: class pending for a flagged one; a jammer’s verb is Jam) and sends the command through Mainframe; the audit log records who engaged what.
  • The block then reads Engaged · IXL-4 VNO · interceptor 2 · ETA 0:21 with Abort. On the map a dashed line runs from the interceptor (the launcher before it is airborne) to the track, ETA 0:21 at its middle and the predicted intercept point as a small cross; a jammer’s line is amber and reads JAM. The interceptor is an own-fleet drone: a friend track, listed in Assets under its launcher.
  • Mainframe steers the interceptor to the track twice a second. If you take control of the interceptor (its lease), the cues pause until you release it.
  • Abort asks once too: a jammer stops transmitting; an interceptor holds and lands where it is and is lost to the launcher.
  • The outcome closes it: Neutralised · destroyed · interceptor 2 · IXL-4 VNO with its time, and a mark on the map where it happened, labelled with the miss distance (✕ destroyed, ↓ forced landing, ↩ returned home; missed in amber). The track then ends. A launcher reads one interceptor fewer (3/4) until it is reloaded.
  • More threats than interceptors: an empty launcher (0/4) stays in each list flagged not ready and cannot be chosen; the tracks nobody can answer keep their place in Tracks (sorted by threat), so what is left unanswered is in view. Reload the launcher (in the simulator: the Simulator UI’s Engagements tab), or engage with another effector. Nothing engages by itself: every engagement is an operator’s.
  • In Replay the section, the line and the outcome read the cursor; Engage With… and Abort are unavailable. Mainframe Settings → Effector Types sets each type’s reach, target classes, Pk, a launcher’s interceptors (capacity, reload, spin-up, climb, airframe) and a jammer’s bands, effect delay and what each kind of drone does when jammed.

Look at… — in the Selection panel’s buttons, the track’s right-click menu and the palette — opens a popover listing the cameras that cover the track, quickest to slew first (ptz-x · 0.8 s · 1.0 km), then the radars that can be tasked. Choose Follow (the camera keeps re-aiming at the track) or Look once, and the field of view (Auto frames the track’s position error, 2–10°), then Look on a camera. The track’s block then shows Cued: VNO PTZ · following (· auto when fusion cued it by itself), with Open Feed (the camera’s video, with its detection boxes) and Stop. The camera’s recognition joins the track’s class within seconds. Commands are not available in Replay.

Fusion can cue cameras by itself: Mainframe Settings → Fusion → Cueing → Auto-cue puts the nearest free camera on a new confirmed track of the chosen identities and classes (within the camera’s rated range), and frees it the Hold after recognised time after the camera has recognised it, or after 20 s if it cannot. An operator’s cue always takes over an automatic one.

Assets → Sensors shows each sensor’s Clock (a column, off by default): fusion’s estimate of how far its time stamps run from true time and how fast that changes (+12 ms · 3 ppm; ≈ until the estimate has settled from aircraft that report their own position). A sensor whose clock is more than 100 ms off raises a sensor clock alert.

A radar also shows its Bias (another column, off by default): how far it reads azimuth and range from where aircraft that report their own position actually were (+1.42° ±0.06 · +58 m ±3; ≈ until the estimate has settled, about a minute of traffic around the radar). Once settled, fusion corrects the radar’s plots by it, on top of the calibration in the sensor’s settings, and its tracks fall onto the reporting aircraft. The tooltip says over how many pairs and whether it corrects now. A sensor’s settings → Bias estimate: Auto (the default: correct once settled), Report only, or Off.

When a radar track and an ADS-B or Remote ID track lie within Mainframe Settings → Fusion → Cooperative distance (250 m by default) long enough, fusion makes them one track. A radar reading a degree or more off puts its track a hundred metres or more beside the aircraft at a few kilometres: the bias correction is what lets the distance stay this tight.

Heights above ground (AGL) are above the terrain under the track, from fusion’s terrain model (a surface model: over forest and roofs, the ground is the canopy and the roof), and heights above sea level use the EGM2008 geoid there. Without the model fusion assumes flat ground at one elevation; Fusion health (heights) says which it uses.

Panel What it helps you do
Voice Join and leave one voice room per panel (pick it from the toolbar chip), mute and deafen it, see who is there and who is speaking, and set each person’s volume. See Voice
Chat Read and write one chat group at a time (pick it from the toolbar chip); mention aircraft, markings, people, times and places; react, reply, edit and delete; attach files; a draft per group survives a reload. See Chat
Panel What it helps you do
Video Wall Compare multiple feeds in a grid
Video Watch one feed with switchable overlays (guides, telemetry, ground scale, markings, route, targets, traffic, home) and the name of the active camera, open the feed’s Actions from the toolbar (a Video Wall tile keeps its Actions button in the corner), capture the current frame, right-click the ground to pin or task there, and replay recorded segments
Telemetry Inspect the selected aircraft’s available measurements
Control Use available flight controls under a control lease, and switch the camera, tilt the gimbal and zoom
Panel What it helps you do
Selection Read what is selected: identity, provider, facts, actions and notes for one object or many; follow a selection group; send any selected object to a chat group
Captures Annotate captured frames from pilots and the analyst; download stills; play, note and download video clips cut from recordings; send the selected still or clip to a chat group
Analyst Work with supported analysis sessions
Assistant Ask for actions in plain words; see Assistant
Charts Compare historical numeric channels across aircraft
Panel What it helps you do
Alerts Acknowledge or resolve alerts
Events Follow operational events and command outcomes by time
Client Log Read, copy and clear this browser’s own log (errors, toasts and diagnostics) to attach to a report
System Check Mainframe and module health in the operational workspace

Settings is not a panel: the Terminal menu opens Terminal Settings… (⌘,) for this browser’s preferences, Mainframe Settings… for the deployment’s rooms, people (users, invites, roles) and configuration, and for administrators its keys and audit log, and Profile… for your own account; see Settings and Access. A layout, local or shared, that names a panel this Terminal no longer has loads without it.

The timeline is not a panel: it is the bar under the workspace, with its controls on the left (see Replay). Drag or click it to review the past, double-click an event tick to jump to it, right-click it for the moment under the cursor (Scrub Here, Send Time to Chat, Copy Time), and toggle it with t or Layout → Timeline Bar. In replay the transport sits around the clock at the right end of the top bar.

Panels show capabilities supplied by the connected modules. Opening a panel does not create a missing sensor, grant a permission, start a paid analysis session, or take control of hardware.

Every asset — an aircraft, a phone, a camera, a controller or a sensor — is Active, Disabled or Removed. Right-click it in Assets (the lifecycle items are last in its menu) or search the palette (⌘K) for Disable V04, Remove V04 or Restore V04.

  • Disable takes an asset out of use without hiding it: it stays in Assets and on the map, dimmed, its State reading Disabled, and its data is still received and recorded. Mainframe refuses commands and control to it, the pickers (missions, control, Send to, the palette) skip it, and a disabled sensor takes no part in fusion. Enable brings it back into use.
  • Remove… asks first, naming what it drops (an aircraft’s live telemetry and alerts; a sensor’s part in fusion). The asset leaves Assets and the map across provider reconnects and Mainframe restarts; history and recordings keep it. The Show removed chip lists removed assets, each with Restore, which brings it back with the same identity.

An aircraft is disabled or removed only on the ground, with no unfinished mission run and no one holding its control; the menu item says what it is waiting for. None of this commands, shuts down or stops the physical device. A sensor’s lifecycle is its document (an administrator’s); every other asset’s is Mainframe’s (entity.manage). Changes require live mode.

A device that sends to the fusion module but is no sensor yet — an unregistered SAPIENT node, an unknown ASTERIX SAC/SIC — shows under Sensors as a Discovered row; Add as Sensor… opens + New → Sensor… with what it said filled in. Nothing waits for approval: a sensor exists once its document does. Assets’ + New adds a base, a flight, an aircraft source (a generic drone, an Autel controller, a phone invite) or a sensor. Removing a base or a flight asks first too.