# Scene Panel: Control Panels

> Operator surfaces that never reach the output.

Glider documentation · The Editor · Web page: https://cgglider.com/docs/scene-panel/control-panels/

Sections of this page: [Output](https://cgglider.com/docs/scene-panel.md) · [Scenes](https://cgglider.com/docs/scene-panel/scenes.md) · [Control Panels](https://cgglider.com/docs/scene-panel/control-panels.md) · [Components](https://cgglider.com/docs/scene-panel/components.md) · [Dragging & drop zones](https://cgglider.com/docs/scene-panel/dragging.md)

+ Panel adds a control-panel layer. The panel note in the UI states the rule plainly: editor tabs only — widgets write data/memory so graphic scenes update; Live never composites these.

- A panel row has no eye: visibility would be meaningless for a layer that never goes to air.
- Clicking a panel opens it as a tab rather than switching the canvas.
- Lock, rename and delete behave as they do for scenes.
- Deleting is blocked when it would leave no layers at all.
- A panel is its scene: one built here or by an agent is edited on that scene.

> **Note:** Build the graphic on a canvas scene, build the operator's buttons and sliders on a control panel, and let data connect the two. See Control Panels for the widgets themselves.