VisTool Role-Based Access for Shared Studios

Shared radio facilities across Australia are busier than ever. From the major networks in Sydney and Melbourne to community stations in regional Queensland, multiple on-air personalities and producers often need to operate from the same physical room at different times of day. VisTool, the studio control software developed by Lawo, was designed with that reality in mind. Its user permission system and role-based access control model allow facility managers to hand each operator exactly the right level of control, without locking the room down between shifts.

The current release of VisTool turns what was once a single-user tool into a layered platform where the studio itself belongs to the institution, not to whoever last logged in. Every action can be tied to a named profile, every preset can be locked to a specific role, and every studio handover can be audited. For broadcasters juggling Triple J shifts in Brisbane, AFL coverage in Perth, and parliamentary broadcasts from Canberra, that kind of structure has become essential.

It also matters when a station collaborates with outside partners. Syndicated news inserts carried through SBS, live crosses with regional talent, and visiting remote engineers can all sit inside one workspace. VisTool's permission framework was shaped by these multi-tenant needs, and it now travels comfortably between stand-alone sites, networked campuses, and entirely virtualised setups powered by RƎLAY.

Permission Tiers Built for Multi-User Workflows

At the heart of VisTool's architecture is a tiered model that separates who can change a setting from who can only use it. Administrators manage the studio, engineers tune the signal path, producers assemble playlists and trigger logic, while on-air talent receives a deliberately limited surface that reduces the risk of mid-show mistakes. Each tier is enforced both at the screen level and at the deeper control layer, so a presenter's fader moves cannot accidentally mute a routed feed to a sister studio in Adelaide.

The system stores profiles locally and pushes them through Power Core nodes when networked. That means a manager in Sydney can update permissions for the Melbourne team without driving across town, and a regional station in Hobart inherits the same template that the capital-city station has already vetted. Because the rules live inside the audio node, they survive reboots and patch changes.

Defining Roles for Hosts, Producers and Engineers

Most Australian broadcasters now think in terms of three primary roles, even when staff rotate between them. The On-Air role exposes a stripped-back mixer view, the Producer role adds routing, logging, and auxiliary playback control, and the Engineer role unlocks full DSP adjustment and I/O configuration. VisTool lets supervisors create hybrid profiles too, which is useful when a Sunday-night host in Perth also needs to record a podcast and trim it before Monday morning.

Engineers can also set secondary restrictions that travel with the role rather than the person. For example, a guest producer covering a fill-in shift on an ABC local frequency might be granted Producer rights but barred from altering mic processing or monitor EQ. That engineer can assign those boundaries once and trust them across the entire campus.

Studio Bookings and Session Boundaries

Shared studios rely on clear session boundaries, and VisTool now treats each login as a self-contained work period. When an operator signs in, the software loads only the presets associated with their role. When they sign out, the desk returns to a default state, and a session report is logged with timestamped actions. That handover discipline is something ARN and SCA commercial networks have asked for repeatedly during recent studio-refresh programs.

The session model also supports overlapping bookings. If two producers in different cities share a logical studio through RƎLAY, each sees only their own workspace, even while drawing from the same underlying Power Core engine. The platform then reconciles which user committed which change when something needs investigating later.

Audit Trails for Australian Compliance

ACMA-licensed broadcasters are expected to demonstrate who touched a control surface and when, particularly when an incident is reported to the regulator. VisTool captures an append-only activity log for every profile, capturing everything from fader nudges to routing changes. Station engineering leads in Brisbane and Canberra can export these logs as part of their compliance packs.

The audit trail is also valuable internally. When something sounds off during a syndicated cut travelling from Sydney to a regional station in Tamworth or Dubbo, supervisors can replay the sequence of operator actions rather than rely on memory. That has proved useful in ARN-owned networks where multiple announcers may touch a single production hour.

Integrating with Ruby Consoles and Power Core

VisTool's permission system does not float independently. It is bound to the physical controls of Ruby consoles and to the routing brain of every Power Core node on the network. When an engineer defines a role, the same definition can lock or expose specific buttons, faders, and programmable keys on the Ruby surface itself. Operators using a touchscreen in a virtual studio and a colleague using a physical fader module in Perth end up with the same logical permissions.

That deep integration is one reason providers such as Cavendish Instruments have specified VisTool alongside hardware from Lawo's catalogue. The studio becomes a single coordinated environment where software permissions and physical switch behaviour agree with each other.

Remote and Hybrid Setups with RƎLAY Virtual Tools

Australia's sheer geography has pushed radio operations towards remote and hybrid models. VisTool talks directly to RƎLAY, Lawo's virtual radio toolset, so a producer broadcasting from a home studio in Geelong or a community volunteer in Broome can carry the same role profile as someone in the city headquarters. Permission settings travel with the login, not with the machine.

RƎLAY also opens the door to guest access for visiting specialists. A visiting audio engineer brought in for a one-off remote broadcast can be issued a temporary profile with engineering rights that expire automatically at a defined time, removing the need for clean-up after the event.

Rolling Out Across Regional Networks

For larger rollouts, VisTool's permission models can be cloned between sites, which suits Australian broadcasters like the ABC and SBS that operate dozens of regional stations under one administrative umbrella. Engineers in Sydney build a baseline template, audit it, and push it to regional centres from Cairns to Albany with the assurance that everyone operates under the same rules.

If a team is exploring how this would slot into an existing facility, the about Lawo Broadcast page outlines the wider Broadcast 3.0 ecosystem and the integration paths available to Australian operations.

What stays with you after all the configuration screens close is this: shared studios behave best when permissions are designed intentionally, roles are tied to people rather than machines, and every action leaves a record. VisTool delivers exactly that combination, which is why so many Australian networks are now standardising on it as their multi-user studio environment.