Builder vs. Client: the two interfaces

Helmo Control is split into two interfaces with different purposes and permissions.

Builder

Role required: Editor or higher

The Builder is where you design your control panels:

• Place buttons on a grid canvas
• Configure what each button does (action type, integration, target)
• Set colors, labels, and icons
• Create multiple Panels of buttons (e.g., "Graphics", "OBS", "Streaming")
• Use the Control Wizard to auto-generate buttons from existing integrations

Think of Builder as the edit mode interface.

Client

Role required: Operator or higher

The Client is where operators use the buttons during a live broadcast:

• Full-screen button grid optimized for fast operation
• ON AIR indicators (buttons glow/change color when active)
• Bottom panel with tabs: Rundown queue, Logs, Editor, Assets
• Keyboard shortcut support for rapid execution
• "Hide panel" mode for maximum grid space
• 12 visual themes to match your operating environment or control-room preference

Think of Client as the live mode interface.

Transition tags on the live Output

Each graphic can carry a transition tag: lower third, bug, fullscreen, or ticker. These tags are mutually exclusive per slot: only one graphic per tag can be on screen at a time. Taking a new graphic with the same tag automatically clears the previous one. This mutex behavior applies not only in preview but also on the live Output, so you can't accidentally stack two lower thirds or two fullscreens on air.

How to switch

In Builder, click the Preview button (top right). Client opens in a new tab. Your operator uses Client; you stay in Builder to monitor and adjust. Changes in Builder appear immediately in Client without refreshing.

Why separate them?

During a live broadcast, you don't want the operator accidentally moving or deleting buttons. The Client provides a clean, locked interface focused on execution. Designers work in Builder before the broadcast, operators work in Client during the broadcast.