Manage screens
The Screens page is the control centre for your display fleet. From here you can see the health of every screen, send remote commands, capture screenshots, and review errors.
Screen status
Each screen shows a connection status:
| Status | Meaning |
|---|---|
| online | The player app has checked in recently and is reachable. |
| offline | The screen has missed its heartbeat window and is unreachable. |
| warning | The screen is reachable but reporting a problem (for example, an error log entry). |
Status is driven by heartbeats the player app sends to the platform at a regular interval. See Screen states for what each state means in detail.
Device details
Selecting a screen shows its device telemetry, including:
- Resolution, orientation, and rotation
- OS, SDK, and app versions
- RAM and disk usage
- Last-seen timestamp
- Geolocation (latitude/longitude), where available
Remote commands
You can send commands to an online screen without leaving your desk:
- Wake screen — wake the display.
- Restart app — restart the player app.
- Clear cache / Clear data — clear cached content or app data.
Commands are queued and picked up by the player on its next check-in. You can view the status of a command and clear pending commands from the screen's detail page.
Screenshots
Capture what a screen is currently displaying:
- Open the screen and go to the Screenshots tab.
- Click Capture Screenshot.
- The image appears in the screenshot history, where you can view or delete it.
Screenshots are also available on a schedule for automated monitoring.
Error logs
Screens report errors back to the platform. Each screen has an Error Logs tab where you can review recent errors. Use the per-screen debug toggle to control whether verbose logging is sent remotely.
Proof of play toggle
Each screen has a Proof of Play toggle that enables or disables playback event reporting for that screen. See Proof of Play for what these events are used for.
Next steps
- Organise screens with screen groups.
- Assign screens to sites.