AERA URBAN / CONTENT MANAGEMENT
Administrator
Your control room is ready.
Create the CMS tables in your verified staging database to start registering screens.
This creates CMS tables only in aerk3634_cms_stage.
NETWORK AT A GLANCE
Overview
Start with a clear view of every screen.
Build your screen network
Phase 1- 01Register a physical screen
Add its site, resolution and timezone.
- 02Review the configuration
Mark it ready when the details are confirmed.
- 03Test simulator pairing
Open Players to test the connection before Android development.
A screen record is
just the beginning.
Test pairing and scheduled browser playback under Players. Connection status confirms heartbeats only. Android playback and proof-of-play are coming in a later release.
NO LIVE PLAYBACK| Screen / Site | Resolution | Configuration | Player |
|---|
No screens here yet
Register a screen or adjust your filters.
“Ready” describes the configuration. It does not mean the screen is online or playing content.
A home for your campaign files.
Enable the Media Library to upload JPEG, PNG and MP4 files into private staging storage. Your existing screen records stay in place.
0 active files0 pending review0 approved
No media here yet
Upload a creative file or adjust your filters.
JPEG, PNG or MP4 · Up to 8 MB per file · 200 MB pilot storage including archived files.
Approval records your content review. It does not schedule playback or certify player compatibility.
From approved files to a screen schedule.
Create ordered playlists and daily schedules. Preview the result here before connecting an Android player.
0 playlists0 planned schedulesPreview only · No player delivery
01 / BUILD THE LOOP
Playlists
Approved files in your chosen order. Assign a duration to every slot.
02 / CHOOSE THE WINDOW
Schedules
Daily windows in the screen’s timezone. Planned schedules cannot overlap. Drafts do not run in the schedule preview.
Schedule preview
Choose a local date and time at the screen. This checks which playlist is scheduled; it does not send content to a player.
Connect your first simulator.
Test pairing, heartbeat status and access revocation using a browser tab. No Android hardware is required for this step.
0 simulators seen recently0 active credentialsHeartbeats only · Playback tested in simulator
01 / AUTHORIZE A CONNECTION
Open simulator ↗Pair a browser simulator
Generate a code for a Ready screen, then enter it in the simulator tab. The one-use code expires after 10 minutes. A screen can have one active simulator.
Enter this code in your simulator. Share it only with the device operator.
This code is shown only now. Generating another invalidates the previous code for this screen.
02 / OBSERVE THE CONNECTION
Simulator connections
A heartbeat is sent about every 30 seconds while the simulator is running. “Seen recently” means a heartbeat arrived within 90 seconds. Browser suspension or network loss can delay updates.
Simulator credentials expire after 72 hours. Revoking a connection immediately blocks its next request. A paired simulator can read approved media from its own screen’s current schedule. No administrator access or billing permissions are granted.
Recent changes
Last 20 workspace changes · times shown in your browser timezone