Build a position by placing elements on its canvas. Start with a section for one part of the job, then add buttons or more specialized sections. Open Position → Position, select the position, then select Open Editor.
A Button is a control that can perform actions and display state. Use one for a direct task such as muting a channel, recalling a scene, starting playback, or taking a prepared route.
A button can use:
Actions that run when it is pressed, released, or operated through an encoder.
Feedbacks that become active when a condition is true and can override its appearance.
Variables that display values such as -12 dB, Camera 2, or slide 7 of 24.
Use a connection preset when one provides a suitable ready-made button. Start with a direct button instead of a workflow when no additional logic is needed.
A Section groups related controls in one area of the position. Use sections to make the workspace match the work: for example, separate playback, monitoring, audio, and routing controls.
A section can contain buttons and nested sections. If its contents exceed the visible area, configure independent scrolling so the additional controls remain reachable. See Organize controls in a section.
A Shift Section provides alternate layers of controls in the same area. It starts with Main and Shift pages.
For example, the main layer can recall PTZ camera presets while the shifted layer saves the current camera position to those presets. See Add secondary controls with a Shift Section.
A Folder Section organizes controls into navigable pages. It starts with a Main page and child folders.
Use it when operators need to browse categories in a fixed area: for example, choosing a studio and then a device within that studio. Always provide clear labels and a visible route back so the current location is not ambiguous.
A Popover keeps additional controls behind one compact launcher. Pressing it opens a temporary panel that can contain buttons and nested sections.
Use it for controls that should remain nearby but do not need permanent canvas space, such as confirmation choices or occasional adjustments. Configure its open direction and dismissal behavior so it does not obscure controls needed at the same time. See Add a Popover Section.
A Router creates an XY-style routing interface from routing resources available to Buttons. Use it when people need to choose sources and destinations, inspect route state, and take routes from a position.
The selected area must be at least 6 × 2 cells or 5 × 4 cells. Routing can change real signal paths immediately, so configure the available sources, destinations, levels, and take behavior before making the section available for production use.
Note
A Router generates a complete routing panel for you from the resources you pick. A Custom Router, described next, instead gives you an empty context that you populate yourself, button by button. Both are labeled Router in the inspector, so check which one you created if you're unsure. See Build a Router Section for the full configuration walkthrough.
A Custom Router is an empty section that owns the current routing selections and displayed state for the controls inside it. Use it to mix and match source, destination, Preset, level, label, and utility controls in a routing panel you lay out yourself. See Understand Custom Routers for how that shared context, its take behavior, and its control modes work.
Folders, popovers, and shared sections can organize the controls. As long as they remain inside the Custom Router, their routing buttons work with the state owned by that Custom Router. A routing button outside it has no Custom Router to operate on.
Routing can change real signal paths. Confirm the permitted sources, destinations, levels, and take behavior before testing the panel against production equipment.
A Shared Section inserts centrally maintained controls into a position. Choose an existing shared section or select Create New Master to create one.
Use it when several positions need the same controls and future updates should be made once. Use an ordinary section when the controls belong only to this position or need to diverge independently.
A Role Section automatically loads the controls and features appropriate to a user's role. It requires a Pro license.
For example, a person can scan an NFC card on a Stream Deck Studio. After Buttons identifies their role, the Role Section presents the controls configured for that role in the same area of the position. This lets several people use the same surface while each receives the features needed for their work.
Use a Role Section when controls should follow the person who authenticates rather than remain fixed for the position. Use a regular, shift, or folder section when everyone at the position should see the same controls.
The editor keeps its runtime state separate from the live position, and layout changes do not become saved configuration until you select Apply.
Warning
Holding Shift and pressing a button in the editor enters Execute Mode and performs its actions against connected equipment or software. Confirm that the action is safe before testing it.
After testing pages, popovers, action steps, or local state in the editor, select Push State to Live only when the live position and its surfaces should adopt that runtime state. Push State to Live does not replace Apply.
