Scenes and Layouts

Scenes are the containers for your visual content. Each scene has a layout that divides the canvas into zones, and each zone holds content.

Creating a Scene

Layouts

A layout defines how the scene canvas is divided into zones.

Built-in layouts

Custom layouts

You can create custom layouts by defining zones with precise pixel positions and sizes. Zones cannot overlap.

Zone Content

Each zone in a layout holds one or more content items. When a zone has multiple items, they rotate on a schedule.

Adding content to a zone

1. Click on a zone in the Designer
2. Click Add Content
3. Choose the content type:
   • Component — A themed, reusable content block
   • Media — An image or video from the Media Library
   • Scene — Embed another scene (for nested layouts)

Zone rotation

When a zone has multiple content items, configure rotation:

Schedule Rules

Scenes support schedule rules that control when they are active. Rules stack — a scene plays only when all its rules are satisfied.

Rule types

Combining rules

Rules combine with AND logic. For example:

• Time Range 09:00-17:00 + Day of Week Mon-Fri = Weekday business hours only
• Date Range Dec 1-31 + Always = All of December

Scene priority

When multiple scenes are assigned to an endpoint, priority determines which plays when schedules overlap. Higher priority scenes take precedence.

Transitions

Configure how scenes transition when switching:

Transition duration is configurable from 0 to 2000ms.

Scene Publishing Workflow

Scenes have a Status that controls whether they appear on live displays:

How it works

• New scenes always start as Draft — they are never immediately visible on displays
• When you are ready, click Publish to make the scene live. This also creates a versioned snapshot
• To remove a scene from live rotation without deleting it, click Unpublish. The scene returns to Draft status
• If all scenes on an endpoint are in Draft status, the endpoint shows a branded holding screen with the endpoint name and a live clock

Content Approval Workflow

When the approval workflow is enabled, scenes gain two additional statuses and follow a structured review process before going live.

Workflow statuses

Simple flow (without approval)

Draft → Published — authors can publish directly at any time.

Review flow (with approval)

Draft → Review → Approved → Published

If a reviewer rejects the scene, it returns to Draft with feedback so the author can make changes and resubmit.

Submitting for review

1. From the scenes list, hover over a Draft scene
2. Click the paper plane icon to submit for review
3. Optionally add notes explaining what changed

Reviewing scenes

Reviewers, editors, managers, and admins can approve or reject scenes that are in Review status:

• Approve (check icon) — moves the scene to Approved status
• Reject (ban icon) — returns the scene to Draft with a required reason

Review comments

Click the comment icon on any scene in Review or Approved status to open the review thread. The thread shows:

• Status change entries (submitted, approved, rejected) with coloured badges
• Free-form comments from any authenticated user
• Timestamps and user avatars

Rejection and resubmission

When a scene is rejected:

1. The scene returns to Draft status
2. The reviewer’s reason is recorded in the review thread
3. The author can make changes and submit for review again
4. All previous review history is preserved

Scene Versioning

Versioning operates at the scene level. Every time you publish a scene, a versioned snapshot is created that captures the complete scene state:

• Scene properties (name, theme, duration, transition)
• Zone content assignments
• Schedule rules
• All referenced content data

You can access version history from the scene’s action menu on the endpoint page.

Version history

The version history panel shows every published version with its version number, timestamp, and the user who published it. Version numbers increment sequentially starting from 1.

Reverting to a previous version

Click Revert on any version in the history to restore the scene to that state. Reverting:

• Creates new scene-scoped content copies rather than overwriting library content. If the original content has been edited in the library since the version was published, the library version remains untouched.
• Records the revert itself as a new version in the history, so no history is ever lost.
• Restores the full scene state: layout, zone content, schedule rules, and content data.