What a position is, how surfaces give a person access to it, and when you need another position or only another surface.
After this section you can:
Explain a position as one person's workspace, not a room, a device or a user account.
Explain a surface as one interface into a position.
Choose between adding a position and adding a surface for a described need.
Explain that editor changes stay in the editor until you select Apply.
Connections are how Buttons talks to devices. Positions and surfaces are how people talk to Buttons. In this section you'll learn the difference between them, and create one of each.
A position is the complete workspace for one person at one operating position, such as sound, graphics, shading, vision mixing or a production desk.
A position holds that person's controls, their navigation (which page or popover they're on) and their state. It keeps all of this separate from every other position, so several people can use the same Buttons system without getting in each other's way. When the sound operator changes page, the graphics operator's panel doesn't move.
A position is not:
A room. A control room may hold several positions.
A device. Devices are connections.
A user account. Who may use or change what is managed separately, under Auth.
A surface is one interface through which a person uses a position: a hardware panel such as a Stream Deck, an iPad, or a browser window.
One position can have several surfaces at once. A sound position might have:
a hardware panel beside the mixer for the controls used most,
a browser on the workstation for a bigger overview,
an iPad for controls needed elsewhere in the room.
These are three ways into the same sound position, not three positions. In the position editor you arrange the surfaces on the position's canvas to match how they sit in the real world. Where two surfaces overlap on the canvas, they show the same controls.
Two Stream Decks assigned to one position, placed side by side on its canvas.
The same person needs another way to reach their controls
Another surface on their position
Another person needs their own controls, navigation and state
Another position
Several positions need the same controls, maintained in one place
A shared section, used in each position
The editor doesn't change the live position until you apply#
You build a position in the position editor. Changes to the layout and controls stay in the editor until you select Apply. The editor also keeps its own state while you test, so opening a page in the editor doesn't move the live surfaces.
That doesn't make the editor harmless. Holding Shift while pressing a control in the editor enters Execute Mode, which runs that control's actions on real equipment. Treat it like pressing the button on a live panel.
Create a position and give it a surface you can open in your browser.
Open Position → Position and select Create. On an empty system, select Create new position.
Enter the LabelPractice Position and select Create Position. Buttons opens Position Configuration.
The Create Position dialog. Enter Practice Position as the label.Position Configuration for a new position. Assigned Surfaces is still empty.
Open Connect → Surface and select Add.
Choose iPad Mini, enter the LabelPractice iPad, and select Create surface. The surface shows Waiting for surface until something opens it. That's expected.
Enter Practice iPad as the label, then select Create surface.
Under Assigned to Position, choose Practice Position, then select Save.
The new iPad surface: Waiting for surface at the top, Assigned to Position below, and Open iPad view on the right.The Assigned to Position list. Pick Practice Position from your own list.
Select Open iPad view. A new browser tab shows the surface as a grid of buttons. The position has no controls yet, so the buttons are empty.
Go back to Position → Position, select Practice Position, and find Practice iPad under Assigned Surfaces.
You now have one position with one surface. If you added a hardware panel too, both would show the same position.
Note
The iPad view opens on the same computer as Buttons here. To open it on a real iPad, Buttons must accept connections from other devices; see Add and attach a surface.
Quiz
Answer the questions for this section. You need 80% to move on.