The main navigation runs down the left side of the interface. Buttons can move items into More when the browser window is not tall enough to display every item.
Some pages and subpages depend on the installed license or enabled features, so they may not appear in every installation.
Press ⌘K (macOS) or Ctrl+K (Windows/Linux) from anywhere in Buttons to open the command palette: a faster way to jump to a page, run a command, or find a resource by name without clicking through the menus.
Start typing to search. With no search text, the palette shows your Recent commands first, then a Context group of commands relevant to whatever page you're currently on, then every other command grouped by area (Navigation, Position, Connections, Workflow, Cuelist, Tags, Routing, Settings, Auth).
Once you type a search, matching commands stay grouped by area, and a separate Resources group appears below them with real positions, connections, and other named resources that match, not just menu items.
Use the arrow keys and Enter to select a result without touching the mouse, or Esc to close the palette without doing anything.
Results respect your access the same way the rest of the UI does: a command or resource you don't have permission for either doesn't appear, or appears greyed out with the reason shown in place of its usual description.
The home page shows system warnings, configured resources, the running Buttons version, and links to community and support information.
A warning on Home is a reason to inspect the affected resource or service before starting production work. It does not necessarily mean every control is unavailable.
Use Position to define the physical operating positions and workspaces in your system.
Depending on enabled features and your access, this area can include:
Position: create positions and edit their sections and controls.
Variables: inspect or manage position variables when that feature is enabled.
Shared: create sections that can be reused in multiple positions.
A position brings together the interfaces used by one person at a physical operating position. It makes those surfaces work together and interact as one workspace, while keeping that person's controls, actions, navigation, and position state separate from other positions. For example, the same sound position could be available through a hardware panel, a browser session, and an iPad.
Use Workflow when a task needs automation or custom logic beyond a direct button action. A workflow can respond to events, evaluate conditions and values, run actions, and exchange data through APIs. For example, it could check whether a connection is online and choose a fallback action.
Use Cuelist to maintain a list of actions. Run them in a determined order for a show, or use the cuelist when a list is more practical than placing every action on an individual button. A cuelist can also be controlled from a position.
Use Tags to organize and filter different resource types. An item can have tags from multiple collections (for example, Studio 1, Audio, and Shared), so plan names around how people find resources.
Use Routing to configure routing resources and to control which source reaches a destination.
The basic pages are:
Route: select, stage, preview, and execute routes.
Presets: save and execute routing salvos. These are different from presets used to create position controls.
Labels: give routing resources clear, meaningful labels.
Ports: inspect routing ports and their configuration.
Depending on enabled routing features, the area can also include:
Virtual
Relations
Rules
Requests
Graph
Projects
Tally / UMD
A routing project groups routing activity so claimed resources, such as tielines, can be released together. Projects can expire automatically or be released manually.
Use Route or a prepared routing control to change an active source. Use the configuration pages to provide meaningful names, valid choices, and clear route status.
Roles: group permissions and assign access to resources.
Sessions: inspect or manage active sessions when that feature is enabled.
Unlike most license-gated areas, Auth stays visible without a paid license tier rather than disappearing from the navigation; it just isn't interactive until the system is licensed.
The first local administrator can access the complete system. Create separate user accounts and grant each account only the resources and operations it needs.
Use Settings for system-wide configuration and maintenance. See Find your way around Settings for what each page covers.
Not every user or license sees every settings page. Read the task-specific guide before changing settings that affect authentication, routing, certificates, backups, or services.
The highlighted main-navigation item matches the job you intend to perform.
The page heading or submenu identifies the exact resource type.
You are editing the intended system, position, connection, workflow, or route.
You understand whether the change affects configuration or immediately controls a connected unit.
For example, changing a button's design under Position edits configuration. Taking a route under Routing → Route can immediately change the source feeding a real output.
If an item is absent, check whether its feature is enabled and included in the installed license.
