Any reachable page
Your intranet dashboard, your status page, your own board.
App Store · Web page
The escape hatch
for everything else.
Every integration this platform does not have has the same workaround: if your own systems can publish the thing as a web page, the screen can show that page. It is not an integration, and knowing the difference is what stops a project going wrong six weeks in.
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.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
Give it a URL
A page you control, or one that is public.
-
Or paste an embed snippet
The console takes one.
-
Give it a zone
Full screen, or a panel beside your media.
-
The page does the rest
It refreshes because it is a page, not because the console refreshes it.
What you get
Six things it does today.
Full screen or a zone
Composition decides.
Live because the page is live
Nothing to re-publish.
Per site
Publish targets facilities.
Fastest route to a hard requirement
When there is no connector, there is this.
Audited like anything else
Every change is recorded against a person.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can it show our Power BI or Grafana dashboard?
If you can expose it at a URL that needs no login, yes. If it demands an authenticated session, no — the player cannot sign in.
Is this the same as an integration?
No, and the difference matters. It displays a page. It does not exchange data, and nothing about the page is monitored.
Can it show a PDF or a spreadsheet?
Office documents have their own route — the console embeds PowerPoint and Excel through Microsoft's viewer.