Zoom Rooms
In plain English
Plain definition
A Zoom Room is a meeting room that has its own Zoom identity. People walk in, start or join a meeting from a tablet on the table, and share a laptop screen to the room display, without signing in on a personal device. Remote attendees can join from another room, a desktop or a phone. In everyday speech "a Zoom room" sometimes just means a meeting link; in Zoom administration it means this licensed room system.
Zoom Rooms is Zoom’s software-based room system: a dedicated computer or appliance in a meeting space runs the Zoom Rooms software, a controller runs the Zoom Rooms Controller software, and together they give the room integrated video conferencing, audio conferencing and wireless screen sharing. Each full room needs a Zoom Rooms licence (or the 30-day trial) and is managed centrally from the Zoom web portal. The constraint that matters most in operation is that settings are inherited down a location hierarchy, so a change made above a room reaches every room beneath it that inherits that setting.
Technical definition
Zoom documents the minimum components of a room as follows:
- Room system: a Zoom Rooms Appliance, iPad, macOS computer or Windows computer running the Zoom Rooms software, connected to the display, camera, microphones and speakers.
- Controller: unless the room system is a touch device, a purpose-built controller, iPad, Android tablet or USB-attached Windows controller running the Zoom Rooms Controller software.
- Optional devices: an additional controller acting as a Zoom Rooms Scheduling Display, and enrolment in Zoom Device Management for remote management.
The room system and controller are paired by entering the Room Code shown on the room display into the controller; the room is then signed in, for example with the room’s Activation Code. In the Zoom Rooms REST API (v2), each room has a type (ZoomRoom, PersonalZoomRoom, Kiosk, StandaloneWhiteboard, SchedulingDisplayOnly or DigitalSignageOnly) and a status of Offline, Available, InMeeting or UnderConstruction.
Operational relevance
For administrators, Zoom Rooms is mainly a fleet of shared endpoints. Day-to-day work is room health, calendar integration and settings governance:
- Deploying a full room needs licences, and managing rooms needs a web portal role with the Zoom Rooms administration privilege. A test room needs no licence but has limited functionality.
- Calendar integration is configured against Google Calendar, Office 365 or supported on-premises Exchange versions, so that the room’s scheduled meetings can be started from the controller.
- Network design matters: Zoom recommends wired networking for the room system, and if the controller is on Wi-Fi, the wireless subnet must be able to reach the wired subnet. If it cannot, change the network or give the controller a wired network adapter.
- From a controller, an administrator can reboot just that controller, or every display, controller and scheduling display in the room at once.
Architecture relationship
Rooms sit at the bottom of a location hierarchy. The account is the top level and holds default settings; optional intermediate levels are Country, City, Campus, Building and Floor; the individual room is the lowest level. A room either keeps its own value for a setting or inherits it from the nearest level above. Only the account owner can create the initial hierarchy (in the web portal under Room Management, then Zoom Rooms, then Edit beside Location Directory); Zoom Room administrators can modify it afterwards. Through the API, a room can only be placed under the lowest enabled location level, such as a floor. Settings are grouped by type: meeting, alert, signage and scheduling_display.
Example
A service desk is told that the boardroom tablet “cannot find the room”. With an OAuth app granted the room:master scope and an account owner or admin role, a read-only call lists the room’s devices:
GET https://api.zoom.us/v2/accounts/{accountId}/rooms/{roomId}/devices
Each device in the response has a device_type (for example Zoom Rooms Computer, Controller or Scheduling Display) and a status of Online or Offline. If the Zoom Rooms Computer is Online but the Controller is Offline, the room software is reporting in, which points to the controller or its network path to the room system rather than the room system itself. A sensible inference, given Zoom’s network guidance, is to check first whether a wireless controller can reach the wired subnet. If the call instead returns HTTP 400 with error code 200, “Zoom Room subscription not found”, the account has no Zoom Rooms subscription to manage.
Common misunderstanding
The common mistake is treating a room’s settings as local to that room. Because rooms inherit from the floor, building and account levels, changing a value at the Building level changes it for every floor and room in that building that has not set its own value. By the same model, a room configured with its own value keeps it when a higher level changes. A second misunderstanding is about licensing. A PersonalZoomRoom consumes a Zoom Rooms licence and gains Pro features only when its pro_device option is enabled.
Related terms
- Zoom Rooms Controller: the software on the in-room tablet or touch panel that starts, joins and controls meetings.
- Scheduling Display: an additional controller device that shows the room’s schedule and, where enabled, lets people make an instant reservation.
- Room Code and Activation Code: the pairing code shown on the room display, and the code that signs a device in as a specific room.
- Location hierarchy: the account, intermediate locations and rooms through which settings are inherited.
- Zoom Device Management: enrolment that adds remote management of room devices from the web portal.
Further reading
- Zoom Support, “Getting started with Zoom Rooms” (updated 2 June 2026): requirements, licensing, preparation and setup.
- Zoom Support, “Using Zoom Rooms location hierarchy” (updated 8 May 2025): levels, inheritance and portal steps.
- Zoom Developer Platform, “Rooms Master API”: room, device, settings and location endpoints.
Checking a Zoom Room before and after a change
Treat any settings change as a fleet change until you know where it is inherited from.
- Confirm health, read-only: list rooms and check the room’s status is
AvailableorInMeetingrather thanOffline, then list its devices and confirm each expected device isOnline. - Find the owning level: check whether the room, its floor, its building or the account holds the value you intend to change, and record the current value at each level before editing anything. That record is your backup.
- Change at the lowest level that needs it: test on one room or a test room first, not at Building or account level.
- Verify: confirm the new value is shown on the target room and that sibling rooms still show their previous value.
- Roll back: restore the recorded value at the same level. Do not delete locations or rooms as a rollback, because those are separate, destructive operations in the web portal.
The next safe decision is usually whether the change belongs at Building or account level at all, or whether it should stay on the rooms that actually need it.
Related reading
Authoritative Sources
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.