LIVEVIEW · FOR WINDOWS DESKTOPS
The screen your team is already looking at is a screen too.
LiveView puts scheduled content over an employee’s own Windows desktop instead of buying a display for it, then disappears completely the moment they are in a call, presenting, or sharing their screen.
- Never
- Steals keyboard focus when it appears
- 0
- Windows or notifications during a call or presentation
- 9
- Positions to pin it, from the tray
- Built in
- Team chat on the same screen — LiveTalk
NOT A KIOSK
It appears, it never steals control, and it knows when to leave.
A dedicated screen is not always the right answer. A reception desk, a shared workstation, an office nobody wants to put a TV in — LiveView is built for the PC that is already there, running the same layouts and the same CMS as every other Live player, without taking over the machine.
Sized and positioned from the CMS
The display profile that already carries a screen’s size and position carries the overlay’s too. Content scales to fit with no letterbox bars, so there is never a transparent dead zone sitting over someone’s desktop swallowing clicks.
Never steals focus
The window surfaces without taking keyboard focus. Whatever you were doing keeps going, mid-sentence and mid-keystroke, exactly as if it had not appeared.
Muted by default
Unexpected sound on a work PC in an open office is disruptive, so audio starts muted with a control to unmute. A layout pushed with volume from the CMS never overrides a local mute.
Minimise, not dismiss
Minimising is a “not right now”, not a “stop”. The player keeps running and the next scheduled item still surfaces. Only Quit, from the tray, is a real stop.
START HERE
One more Live player, built for a desk instead of a wall.
LiveView is a Live player, the same as Windows, Android, Linux, Tizen, webOS and BrightSign. It connects to the same Live CMS, plays layouts built the same way, and reports back the same proof-of-play data. What is different is where the window sits and how it behaves: it lives in a corner of a real desktop rather than owning a whole screen, and it is the CMS profile, not the operating system, that decides its size and position — the same place you already manage every other display.
Proof-of-play only counts what was genuinely on screen: the window has to be showing, the Windows session has to be active and unlocked, and none of the suppression conditions below can be in effect. A monitor gone dark on idle timeout is provably not being read, so it is not counted either.
AT A GLANCE
- Runs as
- A native Windows application in the notification area, not a browser tab.
- Positioned by
- The CMS display profile — the same place every other screen is already managed.
- Disappears during
- A call, a presentation, full-screen video or apps, and Do Not Disturb.
- Requires
- Windows 10 version 2004 or later, or Windows 11.
- Deploys via
- A manual installer, or an MSI for Group Policy, Intune or SCCM.
- Licensed
- Per PC, the same as any other display.
FULL SUPPRESSION
In a call, presenting, or on a shared screen: nothing appears at all.
Not hidden from an audience only. No window, no content, no notification, and the item is not counted as played either.
- Presenting or full screen
- The same signal Windows itself uses to decide whether its own notifications may appear: a PowerPoint slideshow, presenter view, full-screen video, or any full-screen exclusive app, including ones that do not exist yet.
- On a call
- Detected by the microphone genuinely being in use, not by a list of app names. That covers Teams, Zoom, Meet, Webex, Discord and whatever replaces them, without needing an update to know a new one exists.
- Do Not Disturb
- Windows’ own quiet-hours setting is read and respected, on Windows 10 and 11.
- A safety net either way
- The window is excluded from screen capture at the operating-system level at all times, so even in the case detection misses, it cannot end up inside someone else’s shared screen.
WHAT NEVER LEAVES THE DEVICE
Detection knows you're on a call. It never says with whom, or in what.
Telling a call apart from silence means reading which application is holding the microphone. That application's name stays on the device. Every suppression event reported anywhere — to the CMS, into a support log — carries a reason only: call, presentation, full screen, or locked. Never which program you were running.
SETTINGS
Everything the person at the desk needs, nothing they don’t.
Four panes, all real captures from the running application, connected to a live CMS.
Where this player collects its content from. The CMS address, the display name it registers under, and the server key, entered once and reconnected on save.
Chat for this desk, switched on or off with no restart needed. Message toasts and message sound are separate controls, so an open office can keep the badge and drop the sound.
How the overlay behaves on this specific desk, applied immediately: language (Arabic lays the chat panel out right to left), always-on mode for a screen that should never hide, the audio mute, the minimise control, and autostart at sign-in.
What to change and what to quote when something is not working: log detail, and a device panel a support call opens first — version, hardware key, pairing status, one click to copy it all.
LIVETALK
The same screen also carries the team’s chat.
LiveView is not only one-way. LiveTalk adds a chat panel to the same desktop — direct messages, channels and restricted announcements — and it is covered by the same suppression signal as the content: message toasts stay quiet in a call or a presentation too, with an urgent broadcast the one exception.
Direct messages and channels
One-to-one conversations and shared channels, the way any workplace chat splits its traffic.
Announcements
A restricted, one-way broadcast channel for things like HR notices, not a discussion thread.
Polls and reactions
A quick poll with live percentages, and emoji reactions on any message, without opening a reply.
Files and attachments
Send and receive a file in the thread, saved locally rather than opened, because a colleague’s file is somebody else’s bytes.
Read, edited, deleted
A read receipt per message, and both editing and deleting once sent.
Arabic, right to left
The chat panel translates today and lays out right to left in Arabic; the rest of the app is in English for now.
The people and messages in these three panels are a demonstration dataset built for testing, not a real organisation's roster or conversation.
ONE CMS, EVERY SCREEN
A layout built once needs no separate desktop version.
Image, video, audio, HTML, PDF, HLS, embedded content, data sets, tickers and RSS all play in LiveView exactly as they play on a wall-mounted screen, because it is the same Live CMS and the same rendering engine behind both. A layout scheduled to a desktop today can be rescheduled to a lobby panel tomorrow with no rebuild.
Need a screen that owns the wall full time instead — a lobby, a menu board, a video wall spanning several panels? That is Live for Windows, the fullscreen player. Both run from the same CMS; the difference is only whether the screen is dedicated or shared with someone's desktop.
FOR THE TEAM THAT DEPLOYS IT
One desk, or a whole fleet.
A single install for one reception PC, or a policy push to every machine in the building. Same package either way.
A real MSI, not just an installer
Built for Active Directory Group Policy deployment, alongside a manual installer for a one-off desk. The same package installs either way.
Fleet-wide autostart
On a managed rollout, the player starts at sign-in for every user on the machine without a manual first launch — the difference between a fleet that works on day one and one that is dead until each person opens it by hand.
Tray and Jump List
Show now, collect now, settings, view logs and quit, from the notification-area icon and from right-clicking the taskbar button.
Built for a shared PC
On a machine used across shifts, the overlay pauses when the Windows session is locked or switched away and resumes on the next unlock — it never plays, and never counts, to a locked screen.
LiveView: common questions
What is LiveView?
A Windows desktop overlay signage player, part of the LiveSign suite. Instead of a dedicated screen, it puts scheduled content in a small window over an employee’s own desktop, positioned and sized from the CMS, and gets out of the way the moment they are in a call, presenting, or sharing their screen.
How is LiveView different from Live for Windows?
Live for Windows (see our Windows platform page) drives a dedicated screen full time, the same as any other Live player — a lobby panel, a menu board, a video wall. LiveView is built for the opposite case: a PC someone is actively working on, where content has to share the desktop rather than own it, and has to disappear the instant that desk is in a meeting.
Will it interrupt someone who is presenting or on a call?
No. During a call, a presentation, full-screen video or any full-screen app, and when Windows Do Not Disturb is on, nothing appears at all: no window, no content, no notification. It is not counted as played either — an item nobody saw does not count as shown.
What does the detection actually look at, and what does it report back?
Two operating-system signals: the same presentation-mode state Windows uses for its own notifications, and whether the microphone is genuinely in use — which covers any calling app without needing to know its name. What reaches the CMS or a support log is a reason only: call, presentation, full screen, or locked. The name of the application using the microphone stays on the device.
Can I make LiveView stay on screen permanently, like a normal player?
Yes. Always-on mode, in the This PC settings pane, keeps the overlay visible regardless of schedule — useful for a screen that should behave like a dedicated display rather than an interrupt.
What happens if someone minimises it?
It goes to the taskbar, not away. The player keeps running and the next scheduled item still surfaces when its time comes. The only action that stops LiveView is Quit, from the tray.
Does it work on a PC that is shared across shifts?
Yes. The overlay pauses whenever the Windows session is locked or switched to another user, and resumes on the next unlock. It never renders content, and never counts a proof-of-play, against a session that is not active.
Can our IT team deploy it to a fleet centrally?
Yes. LiveView installs from an MSI built for Group Policy, Intune or SCCM, and a managed rollout writes the autostart entry machine-wide so every user session runs the player without anyone opening it by hand first.
What is LiveTalk, and does every desk have to use it?
A chat panel built into LiveView: direct messages, channels, restricted one-way announcements, polls, reactions and file sharing, translated into Arabic with a right-to-left layout. It is a single toggle in settings, off by default until switched on for that desk, and switching it off takes it completely out of the way — no icon, no notifications.
Is LiveView included in the plan price?
It is licensed per PC, the same as any other display, rather than bundled into a flat plan fee. Talk to sales for pricing against your seat count — it is also available as one of the two players on the 14-day free trial, so you can run it on a real desk before deciding.
Want this in writing? Download the LiveView brochure (PDF).
PUT IT ON A DESK
See it appear on your own screen.
Fourteen days, no card, on the PC you are already using. LiveView is one of the two players a trial account can choose.
Deploying to more than one desk? Sales will price it per PC and talk through a Group Policy rollout.