How to Plan AV for a Building With Multiple Tenants and Shared Spaces

A property management team opens a newly renovated amenity floor in a Class A office building. The shared conference center has large displays, ceiling microphones, and scheduling panels outside each door. It looks great. Then three tenants try to use it the same week. One runs Zoom. Another runs Teams. The third just wants to plug in a laptop. The scheduling panel is tied to the building owner's calendar, which none of the tenants can access. And the network the AV sits on makes every IT director nervous. Multi-tenant buildings with shared AV spaces have challenges that single-tenant environments don't. Platform neutrality, network separation, booking logistics, and long-term flexibility all need answers before the first room is built.

Author

Spye

Editor

minutes read

Posted on

March 30, 2026

Audio Visual

Key Takeaways

Shared conference rooms must be platform-neutral, supporting Zoom, Teams, Webex, and BYOM without requiring tenants to adopt a specific ecosystem.

Network architecture should keep building-managed AV separate from tenant networks, with BYOM connectivity on isolated guest infrastructure.

Room scheduling requires a platform that operates independently of any single tenant's calendar.

Digital signage in common areas should be building-managed with a centralized CMS.

Standardized AV across shared rooms reduces service costs and gives every tenant the same reliable experience.

Why Multi-Tenant AV is Different

In a single-tenant building, the company picks a UC platform, IT manages the network, and every room runs the same way. Multi-tenant buildings break all of those assumptions.

The building owner controls common areas but doesn't control:

What conferencing platforms tenants use

What IT security policies they enforce

How they prefer meetings to work

Whether their devices can connect to shared infrastructure

The core tension is simple: the building owner is responsible for the technology, but the tenants are the ones who use it. If the AV requires a specific platform or creates a security concern, tenants stop booking. The tenants who avoid certain rooms almost always do so because the technology doesn't work reliably for them.

Platform Neutrality is Non-Negotiable

For multi-tenant buildings, BYOM (Bring Your Own Meeting) should be the default. A BYOM room lets any user walk in, connect via USB-C or wireless, and use whatever conferencing platform their organization runs. The room provides display, camera, microphones, and speakers. The user's device provides the meeting and credentials.

This doesn't mean the room can't also have a dedicated Zoom or Teams appliance. The key is that it's an option, not a requirement. The hardware needs to support both paths:

USB-C connectivity at the table for direct laptop connection

Wireless presentation as a fallback

Display and audio that accept input from both a room appliance and a connected laptop without switching cables or settings

When we designed spaces for Jamf's Minneapolis office, the rooms were built around Zoom Rooms to match their platform. For multi-tenant shared spaces, the same hardware quality applies but the platform layer stays open so every tenant in the building gets the same experience.

Network Architecture for Shared AV

Every tenant IT department has legitimate concerns about shared infrastructure. They don't want their devices on a network they don't control, and they don't want building AV on theirs. The solution is three layers with clear boundaries:

Building AV VLAN. Displays, cameras, microphones, controllers, and scheduling panels. Managed by the building's IT or MSP. No tenant traffic touches it.

Guest/BYOM network. Separate segment for tenant devices in shared spaces. Isolated from building AV and from every tenant's internal systems. Configured with enough bandwidth and QoS for video conferencing.

Tenant networks. Completely separate. Tenants who need their corporate network in a shared room use their own VPN on their own device.

This lets the building owner manage and service AV without involving any tenant's IT team. Tenants use the rooms without exposing their network. Both sides get what they need.

Scheduling Across Organizations

Room booking can't rely on one company's calendar. If scheduling is tied to the property manager's Microsoft 365 tenant, employees at companies on Google Workspace can't check availability or book from their native app.

The practical approach is a building-managed platform that works independently:

Tenants book through a web portal, mobile app, or the panel outside the door

The room sends confirmations directly, no cross-tenant calendar sharing required

The panel shows real-time availability and allows on-the-spot booking

Proximity sensors wake the screen when someone approaches

This is the kind of scheduling experience that drives actual adoption instead of sitting unused.

Digital Signage in Common Areas

Lobbies, elevator banks, and amenity floors all benefit from signage. But in a multi-tenant building, the content management model is different.

The building owner needs a system that handles announcements, wayfinding, and brand content without depending on any tenant's IT resources. Some buildings also give tenants the ability to push content to screens near their leased space, which requires multi-zone, multi-permission management.

Spye's SpyeWorks platform supports exactly this: unlimited display configurations, custom dimensions, multi-zone layouts, and scheduled playlists from a single CMS. The building operator runs lobby displays from one interface while tenants manage their own floor screens. For simpler deployments, SpyeSign provides a cloud-based option with built-in templates.

Standardize the Rooms, Simplify the Service

When a building has six or eight shared rooms, the temptation is to customize each one. This creates a maintenance problem that compounds.

Standardize around two or three types: small huddle, mid-size conference, large meeting space. Each gets the same hardware, control interface, and user experience. A tenant who learns the 4th-floor room can use the 8th-floor room identically. Same components, fewer spare parts, one troubleshooting playbook.

Our CLAM System 3.0 was built for repeatable deployment:

Standardized mounting geometry, cable routing, and service access

A building with 15 rooms installs in a fraction of the time custom would take

Front-access design lets one tech swap components in 60-90 minutes

No lifts, no display removal, no extra hands needed

For building owners managing shared AV as a tenant amenity, that consistency is the difference between something that builds loyalty and something that generates support tickets.

Planning for Tenant Turnover

Multi-tenant buildings have a reality single-tenant environments don't: tenants leave. New ones arrive. The technology preferences in the building shift over time.

A Zoom-heavy building now might be Teams-heavy in three years. Room hardware changes on a 5-to-7 year cycle. But the conduit paths, structural backing, and network drops behind those walls should support whatever comes next.

Platform neutrality handles the software side. On the infrastructure side, invest in conduit capacity, network backbone, and power provisioning at a level that accommodates future technology. Getting the infrastructure right during construction is the highest-ROI decision a building owner can make.