Bitfocus AS
logo
logo
Bitfocus AS
logo
logo

Loading...

Bitfocus

Subscribe to our newsletter

The latest news, articles, and resources, sent to your inbox.

FacebookInstagramGitHubYouTubeLinkedIn

Products

  • Buttons
  • Companion

Integrations

  • Supported Devices
  • Developer Community
  • Connection Development

Support

  • Support Overview
  • Documentation
  • Video Tutorials
  • Community Forum

Sales

  • Resellers & Integrators
  • Buttons Pricing

Updates

  • Case Studies
  • Events & Trade Shows
  • Press Releases
  • Product Updates
  • Webinars

Legal

  • Legal Overview
  • Privacy Policy
  • Buttons EULA
  • Terms & Cookie Policy

Company

  • About us
  • Press kit
  • Careers
Co-funded by the European Union

Our Bitfocus Workflow 2.0 project is co-funded by the European Union’s Creative Europe programme. About the project

© 2026 Bitfocus AS. All rights reserved.

  1. Home
  2. Academy
  3. Buttons Foundations
  4. Finding your way around

Section 5 of 79 min

Finding your way around

What each area of the main navigation is for, how the command palette gets you anywhere, and what to check before you change anything.

After this section you can:

  • Pick the right main-navigation area for a described task.
  • Use the command palette to jump to a page or find a resource by name.
  • Run the checks to make before any change.
You now know the main building blocks. In this section you'll learn where each of them lives in the interface, and the fastest way to get there.

The main navigation#

The main navigation runs down the left side of Buttons. Its areas match the building blocks:
Area
What it's for
Home
An overview: system warnings, configured resources and the running version
Position
Create positions and edit their sections and controls
Connect
Add connections, discover NMOS resources, add surfaces and assign them to positions
Workflow
Build automation and custom logic
Cuelist
Build and run ordered lists of actions
Tags
Organize resources with labels from several collections
Routing
Take routes, and manage routing Presets, labels and ports
Auth
Manage users and roles
Settings
System-wide configuration and maintenance
Home, with the main navigation on the left and the running version at the top right. This screenshot is from an older version, so your Home page looks a little different.
When the browser window isn't tall enough, some items move into More. Some areas and pages depend on your license and on which features are on, so not every installation shows every one. Auth is the exception: it stays visible without a paid license, but you can't use it until the system is licensed.
A warning on Home is a reason to check the resource it names before you go live. It doesn't mean everything is broken.

Note

Buttons 1.9 added an MCP server, which lets an AI assistant such as Claude work with Buttons using your access. It's in beta, and it's off until an administrator turns it on under Settings → MCP. You don't need it for this course.

The command palette#

Press ⌘K on macOS or Ctrl+K on Windows and Linux, from anywhere in Buttons, to open the command palette.
  • Start typing to jump to a page or run a command.
  • Your search also finds real resources by name, such as a position or a connection, in a separate Resources group.
  • Use the arrow keys and Enter to choose, or Esc to close.
  • Commands you don't have access to are hidden, or greyed out with the reason shown.
Once you're used to it, the palette is usually faster than clicking through menus.

Check before you change#

Before you change anything, confirm:
  1. The highlighted item in the main navigation matches the job you mean to do.
  2. The page heading names the exact type of resource you mean to change.
  3. You're working on the right system, position, connection, workflow or route.
  4. You know whether the change edits configuration or controls a device straight away.
The last check is the one that matters most. Changing a button's design under Position edits configuration, and nothing happens on the live surfaces until you select Apply. Taking a route under Routing → Route can change a real output the moment you do it.
Read more in the docs:Find your way around Buttons,Understand positions

Try it

In your own Buttons installation.

  1. Open Home. Find the version of Buttons you're running. In the Connections list, find Practice ATEM: its status dot is red. Point at the dot to see why: Disconnected. That's exactly the kind of warning to check before going live.
  2. Open each area in the main navigation once. In each, find either one resource you created in earlier sections or the message shown when the area is empty.
  3. Press ⌘K or Ctrl+K, type Practice, and use the Resources group to open Practice Position.
  4. Open the command palette again, type Routing, and use it to open the Routing area.
  5. For each task, name the area you'd use:
  • Give a new colleague an account.
  • Add a Stream Deck and attach it to a position.
  • Rename a router port so operators recognise it.
Check your answers: Auth, Connect, then Routing (its Labels page).

Quiz

Answer the questions for this section. You need 80% to move on.

  1. Question 1
    1.

    You need to add an audio mixer to Buttons. Which area do you open?

  2. Question 2
    2.

    What is the fastest way to open a position called Sound from anywhere in Buttons?

  3. Question 3
    3.

    Home shows a warning about one connection. What does it mean?

  4. Question 4
    4.

    Which of these changes can affect a live output straight away?

  5. Question 5
    5.

    Auth appears in the navigation but nothing on it can be selected. What is the most likely reason?

0 of 5 answered

PreviousRouting basicsNextChoosing a control method
Buttons Foundations
  1. 1What Buttons is
  2. 2Positions and surfaces
  3. 3Variables and feedbacks
  4. 4Routing basics
  5. 5Finding your way around
  6. 6Choosing a control method
  7. 7Wrap-up and final quiz

In this section

  • The main navigation
  • The command palette
  • Check before you change
  • Try it
  • Quiz