Documentation

Appearance

Build a remote signage application ​

Remote signage combines screen players into one venue experience. Apply the remote signage kit to a Product Application, map the player role to its Device Class, publish a version, and provision the customer instance.

Split the place from the player ​

Open the venue from Networks for:

  • all screens at this place
  • expected and applied content
  • player, display, and sync health
  • screens that need attention

Open an enabled player device and use Controls for this screen and its vendor Device Class UI. Remote signage does not add a product section to the sidenav.

Screen estate workplace showing venue screens, expected content, and player health
The network is the venue-wide screen workplace.
Signage player device Controls tab
The device page stays scoped to this screen player.

Model content honestly ​

Keep the expected content generation separate from the generation a player reports as applied. Show screenshot freshness and player connectivity so an operator can tell a stale preview from a display fault.

Use a customer-controlled media delivery contract and restrict accepted media types. Do not put CDN credentials, private source URLs, or customer media in documentation screenshots.

Verify before handover ​

  1. Place each player on the correct venue network.
  2. Confirm expected content and applied generation match.
  3. Disconnect one player and confirm the venue shows the exception.
  4. Reconnect it and verify the player catches up without duplicate work.
  5. Confirm another customer cannot see the venue, screens, or content.