Facilities, not folders
A real object with its own screens, content and default.
Core platform · Facilities
Every site is
its own thing.
A facility is a branch, a building, a depot or a region. It holds its own screens, its own default, and its own content — so a chain is one console rather than forty logins.
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.
-
One facility per place
A branch, a building, a depot, a region — whatever your estate is actually divided into.
-
Screens belong to a facility
Paired by typing the registration code the screen puts up.
-
A default you land on
Set Default, so the console opens where you work.
-
Switch from the header
Without logging out or hunting through a list.
What you get
Six things it does today.
Pairing by code
The screen shows a registration code; you type it in once.
Tags and filters
So a fleet of four hundred is searchable rather than scrollable.
Device profiles
Orientation, position, width and height, with many screens on one composition.
Counted on the dashboard
Total facilities, active screens and disconnected screens, as headline tiles.
Scoped by group
Facility access is part of what a group can reach.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
How many screens can one facility hold?
There is no fixed number. Any limit comes from the plan your partner built, as an access rule on a feature.
How does a screen join a facility?
It displays a registration code. You type that into the console once, and it belongs to that facility from then on.
Can someone be restricted to one site?
Users belong to groups, and facility access is part of what a group decides.
What runs on the screen itself?
An Android player app on a display you own.