Playlists
An ordered list of items, each with its own duration. Reorder by dragging. A playlist can be used on one screen or on every screen carrying a tag, which is what keeps a network consistent.
The content management system is where the work happens: media in, playlists built, templates applied, approvals given, schedules set. The screens are the easy part.
An ordered list of items, each with its own duration. Reorder by dragging. A playlist can be used on one screen or on every screen carrying a tag, which is what keeps a network consistent.
Layout zones hold your type and your colours: a main area, a sidebar, a ticker and a clock. Build the template once, and every location fills it with its own content without rebuilding the design. A price list, a menu board and a notice board are all templates with different zones.
A web page item shows a live dashboard, a menu system or an internal page as it is, so the screen follows the source instead of following someone remembering to re-export a picture.
| Role | Can do | Cannot do |
|---|---|---|
| Viewer | See screens, playlists, schedules and reports | Change anything |
| Editor | Upload media, build playlists, draft schedules | Publish to a group that requires approval |
| Approver | Everything an editor does, plus approve and publish | Change billing or workspace settings |
| Admin | Everything, including roles, billing and integrations | Nothing is hidden from an admin |
Every role can be scoped to a location or a group, so a store manager works on their own screens and cannot reach the rest of the network. A group can require approval, which puts a second pair of eyes between a draft and 40 walls.
A weekly grid covers the ordinary week. Dayparts split the trading day, so breakfast, lunch and evening differ. Dated campaigns sit on top for the weeks they run and step aside afterwards, returning the screen to its normal week without anyone tidying up.
Every publish is recorded with the person, the time and the screens it reached. On the Network plan that record is a full audit log. Paired with proof of play, it closes the loop: who sent it, when it went, and what the screen actually drew.
Upload once, schedule everywhere, approve before it lands, and read what played. That is the whole content management system in one sentence.