A 22-person marketing agency had four meeting rooms and a wall TV that ran the agency logo for two years. The agency manager’s job was to keep the rooms booked; in practice, it was breaking up arguments about whether Room B was free at 3pm. (Illustrative scenario, not a customer account.)
The fix took about 20 minutes: one calendar widget per room, four widgets in a row, each rendering today’s bookings with a green Now badge on the in-progress event. The arguments stopped.
This post is the playbook for that screen. It’s one pattern in the office TV dashboard cluster. The hard parts aren’t the wiring — they’re the privacy defaults, the right refresh tier, and three failure modes that turn a useful screen into wallpaper.
What a wall room-status board is
One screen showing today’s meetings for every meeting room at a glance — bigger type (60–80 point), at most four or five rows per widget, no scrolling, a single colour cue for the in-progress event (the Now badge). A laptop calendar is something you study; a wall screen is something you glance at. Eight rooms in tiny text doesn’t read; four rooms in big text does.
Different from a vendor room-booking system — Robin, Teem, Envoy at the enterprise end, or any of the per-screen digital-signage CMSs (Yodeck, ScreenCloud, OnSign TV, TelemetryTV, Rise Vision) — there’s no new vendor. The data is yours, the calendar is yours, the screen is yours. The full vendor landscape is in the digital-signage comparison cluster.
What to show — and what to leave off
The minimum useful widget: room name, today’s bookings, with a Now badge on the current event. Anything else is redundant with the laptop calendar or a privacy problem.
The privacy rule: don’t put meeting titles on a public screen. Real-office titles are sometimes things you’d rather not have on the wall — “Layoffs — final review,” “Comp conversation — VP Eng,” “Termination — Jane D.” are not hypothetical. The widget’s showPrivateEvents: 'show' | 'mask' | 'hide' only acts on events the feed itself marks PRIVATE — it swaps the title for Busy or hides the event. For the broader case, title suppression has to happen at the source calendar. Google Workspace resource calendars and Microsoft 365 room mailboxes both have a per-calendar “free/busy only” toggle; that’s the lever that takes sensitive titles out of the wall feed before dotBlast sees them. Default to free/busy at the source; opt in to titles only after an explicit team conversation.
Setup A: Google Workspace (resource calendars)
Every meeting room in Google Workspace has its own resource calendar — a calendar object that represents the room rather than a person. Reference: Create buildings, features & Calendar resources on Google Workspace Help. Sequence:
- Audit and rename in the Google Admin console → Menu → Directory → Buildings and resources → Overview, then open Resource management. Some offices have inconsistent names (“Conf Room A”, “Boardroom”, “room-1”). Standardise first — the wall widget shows whatever name the calendar exposes.
- Get the private iCal URL for each resource calendar: Google Calendar → Settings → the room’s calendar → “Integrate calendar” → copy the Secret address in iCal format URL.
- Set the room calendar’s sharing to “See only free/busy (hide details).” This is the source-side privacy lever — once it’s on, dotBlast never sees titles. One gotcha: with rooms shared as free/busy, your team may lose the ability to book them until an admin ticks Resource booking permissions → “Allow users to book resources that are shared as ‘See only free/busy’” — see Allow Free/Busy Google Calendar room booking.
- One calendar widget per room in dotBlast:
calendarUrl= the iCal URL,daysAhead: 1,maxEvents: 5,showPrivateEvents: 'hide'. Reads today’s bookings with a green Now badge on the current event.
The 4-room Google Workspace setup takes about 20 minutes.
Setup B: Microsoft 365 (room mailboxes)
The Microsoft 365 equivalent is a room mailbox — an Exchange Online mailbox. Reference: Create Room and Equipment Mailboxes on Microsoft Learn. Sequence:
- Confirm each room has a room mailbox in the Microsoft 365 admin centre → Show all → Resources → Rooms & equipment (the standalone Exchange admin centre route was retired; rooms now live under the unified Microsoft 365 admin centre).
- Verify auto-processing is enabled. On by default; without it, every meeting request stays tentative and the wall screen flickers.
- Publish the room mailbox as an iCal share link. Outlook on the web → the room mailbox → Settings → Shared calendars → Publish a link. (dotBlast reads iCal/ICS feeds; there is no Microsoft Graph connector.)
- Set the calendar’s permissions to “Can view when I’m busy” for anyone outside the room’s mailbox.
- One calendar widget per room in dotBlast — same config as Setup A.
The 4-room Microsoft 365 setup takes about 15 minutes.
The three things that always go wrong
Every office that has run a room-status board for more than a month has hit at least one of these. They’re mechanical, and they’re fixable.
1. The wrong calendar is the source of truth. Somebody sets up the widget with the team’s shared calendar instead of a room’s calendar. The team calendar has names and titles; the room calendar (after the source-side privacy step) has only free/busy. If your wall screen shows names and meeting titles, you’re reading the wrong calendar — switch to one widget per resource calendar (Google) or room mailbox (M365).
2. The screen drifts out of sync, and the cheapest plan won’t fix it. The calendar widget is infra-heavy (server-side iCal fetch + parse + RRULE expand + per-URL cache), so its refresh floor is the infra-heavy tier: Free 60 min, Starter 5 min, Pro 60 s, Business 15 s. dotBlast also caches each feed for 5 minutes, and Google/Microsoft iCal publication itself can lag a minute or two. Practical reading: expect minutes, not seconds; Pro is the plan that gets you to a roughly one-minute floor. Calibration: book a test meeting, give it two minutes, then check. If it still hasn’t updated after five, the data source or refresh path is wrong — Starter isn’t too slow, your URL or feed is.
3. The screen leaks sensitive meeting titles. The widget defaults to showPrivateEvents: 'mask', which only hides events the feed marks PRIVATE. If your room calendars publish titles to anyone who can read the iCal URL (a common default), the wall screen renders those titles. Two fixes: source calendar permissions to free/busy-only (Setup step 3), and showPrivateEvents: 'hide' on the widget as a second line of defence. Pre-launch test: walk past the screen as a guest. Anything that wouldn’t survive a guest reading it is the bug.
When this is the wrong read
Three routing notes:
- More than 10 rooms or hybrid Google Workspace + Microsoft 365? The configuration job becomes an integration project; a vendor room-booking system earns its keep. This playbook is for the 3–8 room SMB office.
- No wall TV yet? Start with the office TV dashboard guide.
- Want the room-status board alongside other wall patterns — sales leaderboard, internal announcements, daily standup tracker? The five-use-case listicle shows small teams running two or three on the same TV, rotating across the day.
Frequently asked
How much does it cost? All-in for one wall TV: €0 if you already own one (€200–€400 is a typical band for a new 43” 4K as of mid-2026 — actual street prices vary), plus the software. dotBlast’s pricing uses plan-based device allowances — Free 1 device, Starter 3, Pro 10. No per-screen licence fee.
Do I need to be a Google Workspace or Microsoft 365 admin? Briefly, yes — the resource-calendar and room-mailbox steps require admin access. The dotBlast side is one account holder: dashboards are single-owner, so the widget config lives on the account that owns the dashboard. Anyone with the device link can view the wall screen unauthenticated.
Can I show meeting titles if the team agrees? Yes, but treat it as an explicit decision. Default to free/busy at the source calendar. If the team wants titles on the wall, flip the source calendar to full details and switch the widget’s showPrivateEvents to 'show' after a one-team-meeting conversation about what’s safe to display.
Where this fits in the cluster
This post is the deep-dive for meeting-room availability — one of the twelve SMB use cases for wall screens and one of the five office TV dashboard patterns. The wider cluster:
- Buyer’s-guide perspective: The office TV dashboard guide.
- The sales leaderboard playbook — the other common office TV pattern.
- Team dashboard best practices in remote and hybrid teams.
- Inspiration: the twelve use cases hub.
- Pricing: /pricing.
One iCal URL per room, a TV, a Wi-Fi connection — that’s all you need for a working room-status board on the wall in 20 minutes. The data source is already paying you to exist; the wall screen is just the read-only view.