Skip to content
Knowledge base

Displays

Design and schedule screen content, with preview and device availability boundaries.

4 min read · 3 sections
On this page

Displays authors advertising programmes and approved operational dashboards for dedicated screens. The work area is currently in preview. Implemented workspace/player behaviour is not evidence of installation or acceptance on a particular Samsung panel.

Workspace, screens and design studio

SectionWhat it contains
ScreensScreen inventory, Site/Space, dimensions, orientation, rotation, timezone, tags/group, programme selection, pairing and device state.
StudioCreate/edit designs in Structured layout or Canvas mode, using the shared document renderer.
ScheduleCalendar/rules, recurring or dated programme assignments, campaign windows and previews.
LibraryUploaded media with review, classification and retirement.
Playlists & programmesOrdered designs with slide duration, then programme composition for publication.
SourcesAvailable source catalogue, source-record review, approved notices and publish/withdraw actions.
DistributionScreen groups, design sharing and separately reviewed Group publication.
Playback evidenceDiagnostics live on Screens. The legacy ?section=reports deep link opens Screens.

Create a screen with its actual Site, optional Space, dimensions/orientation, player rotation and Site timezone. Use Pair to obtain a device pairing flow; paired player credentials are separate from staff sign-in. Device revocation is an explicit action.

Create a design with name, canvas, starting layout and audience. The editor supports authored text, media, QR destinations and permitted module widgets; Structured and Canvas views edit the same versioned document. Canvas controls include dimensions, background, snapping, placement, typography/alignment, fill and media fit. Draft saves do not change an existing published programme. Review uploads before using them; retiring media affects its eligibility.

Create a playlist of designs with durations, assemble a programme, then choose that programme for a screen or schedule. Preview publication, review the audience and sources, and publish an immutable revision. Rollback also has an explicit review and does not revive revoked source authority.

Scheduling, sources and distribution

Schedules resolve temporary override, dated assignment, recurring assignment and default in that order. At equal level, local assignments outrank Group ones; equal-precedence overlaps block publication. Site timezone, overnight windows, exclusions and campaign expiry are part of the publication, not a browser-local assumption.

Source bindings check each enabled source module, capability and exact Site/Space. They renew approved live facts within the frozen layout. Public Sport needs an explicit display approval, not only a private screening selection. Talent-only performances need confirmation/promotional approval. Bookings menus use published versions; public EPOS retail prices and eligible ordering offers have separate review. Generic private Messages channels are not copied onto a screen.

Management metrics retain source meaning: expected covers are not occupancy, planned shifts are not attendance, stock is not sellability and till delivery is not order ready. Missing observations remain missing, not zero. Guest names need explicit opt-in and bookings.guests.view; management publication does not grant blanket private-data access.

Group distribution requires an actual shared Group and authority at every selected destination. Each destination reports its own result. Media keeps its original owner so withdrawal reaches distributed/adopted copies. Management comparisons keep business, Site, seller and currency labels separate; sibling membership alone is not cross-business permission.

Offline playback and permissions

A player stages complete signed bundles, verifies media hashes and activates atomically at a slide boundary. Failed downloads or insufficient storage keep the last valid bundle. It caches shell, layout, fonts, media, recurrence rules and source snapshots. Private cached content uses a persisted device key.

All three audiences retain their last authorised programme during an outage and restart. An offline device cannot learn revoked access, disabled modules, changed prices or cancellations. Successful authenticated reconnection persists revocation and purges revoked content before replacement downloads; later fetch failure cannot restore it. Network failure alone does not invent revocation.

Cached future coverage is bounded, up to 35 days where the source supplies it. Exhausted coverage uses a fallback instead of claiming nothing is scheduled. Dated financial snapshots stay dated; unreliable clock state suppresses schedule-dependent claims. Playback telemetry proves software reports, not screen power or audience impressions. Browser restart acceptance needs a persistent kiosk profile; Samsung QMC packaging/install/panel controls need real device qualification.

CapabilityResponsibility
displays.viewRead permitted screen/programme workspace.
displays.design.manageAuthor designs, media and design-library work.
displays.publish.publicPublish public-audience content.
displays.publish.staffPublish staff-audience content.
displays.publish.managementPublish management-audience content with source authority.
displays.devices.managePair/revoke players and handle device health work.
displays.settings.view, displays.settings.manageSettings reach and authority.

Enabling Displays and assigning a person Displays capabilities are separate. The implemented /displays/settings route mounts the Displays workspace and initially opens Distribution, including the offline-operation explanation. Screen defaults, device controls and publication review remain on their operational screens. Disabling the exact entitlement stops authoring/renewal and clears devices on the next authenticated handshake; offline copies persist until that contact.

Available features depend on your workspace, permissions and connected services. Preview and setup requirements are described in each guide.

Back to the knowledge base