Facilities as first-class objects
Every site, branch or region is a facility holding its own screens, with a switcher in the header and a default you land on.
Enterprise
Hundreds of screens,
one estate.
At enterprise scale the content is the easy part. What matters is who can publish, to which sites, with what record, and how quickly you find the screens that are dark. All four are first-class objects in the console.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up — a display a customer stands in front of, driven by a player that fetched it on its own.
What goes on the screens
Six things worth putting up.
Every one of these is ordinary media, arranged in Composition and sent out by Publish. Nothing here needs a separate system.
Groups and users
People belong to groups, and groups decide what they can reach.
Audits
Created, updated and deleted, with the person against each.
Access rules on features
A plan's features carry typed limits — screens, storage, users — set by your partner rather than by a fixed tier.
Live Monitoring at scale
Total active and total disconnected, counted per organisation and per facility.
One library, in folders
The estate shares its media rather than each site collecting its own.
Where the screens go
Four walls that earn it.
-
Head office and regional hubs
The estate view, and the announcements that go everywhere.
-
Every site you operate
Local content, published locally, within a group's reach.
-
Operations and NOC walls
Which screens are dark, as a headline number.
-
Reception and shared spaces
The brand-facing half of the estate.
How it is run
Four steps, then it runs itself.
The same four steps whether you have four screens or four hundred. This is the real console, not an illustration.
-
Add facilities, pair screens
One facility per site, branch or building. A screen joins by showing a registration code, which you type in once. Switch between facilities from the header.
-
Upload and compose
Media goes into the library, in folders, with tags. Composition arranges it into zones — your own files, plus App Store apps like weather, news or a ticker.
-
Publish three ways
On a schedule, with day sequences. Or QuickPlay, which the console describes as displaying content instantly for a flash sale or an emergency. Or as the default composition a screen falls back to.
-
Check it, without going there
Live Monitoring reports each screen's state. Take Screenshot shows what one is really displaying. Reload, clear the cache or reboot it remotely.
What it fixes
The three complaints we actually hear.
- Local teams need to publish, but not to everyone.
- Groups decide what a person can reach; facilities decide where content lands.
- A compliance review asks for a change history.
- Audits records every create, update and delete against a named person.
- Nobody has a live count of the estate.
- The dashboard counts facilities, storage, active screens and disconnected screens as four tiles.
Set it up as
The solutions this usually becomes.
Nearby
Other industries with the same problem.
Questions
What enterprise teams ask first.
How are limits set at our scale?
Limits are attached to features as access rules inside the plan your partner builds. There is no fixed tier we impose.
Is there single sign-on?
No. Users and groups are managed in the console. SSO has not been observed in the product.
Can it run on our own infrastructure?
On-premise hosting has not been confirmed. Ask us and we will get a direct answer from the product team.
Who do we buy from at this size?
A ScreenQube partner, who assembles the plan and its access rules and is who you deal with.
Put it on every screen.
Talk to us about becoming the partner who sells it.
We will introduce you to the partner who covers your region.