PowerPoint and Excel
The two formats the console names.
App Store · Office documents
The deck that already
exists, on the wall.
Most organisations already keep the thing they want on a screen in a PowerPoint file that somebody updates weekly. Exporting it to images every week is the step that quietly kills the project.
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.
-
Point it at the file
A PowerPoint or Excel file reachable at a URL.
-
Microsoft renders it
Through the Office online viewer, not through the player.
-
Give it a zone
Full screen, usually.
-
Update the file, not the screen
The screen follows the document.
What you get
Six things it does today.
Update the source
No re-export, no re-upload.
In a composition
Beside your own media if you want.
Per site
Publish targets facilities.
Scheduled
Appears and goes with the composition.
Owned by the team that owns the file
Rather than by whoever runs signage.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can it read a file from SharePoint?
Only if the viewer can reach it. There is no SharePoint connector in the evidence we have.
Does it advance through the slides?
That is the viewer's behaviour, not the console's. Check it with your own deck before relying on it.
What about Google Slides?
No Google connector appears. A published Google Slides link would be a web page — use the web-URL app for that.