A takeover temporarily replaces normal Pub display programming with a curated group of images or short videos. It is intended for an event that needs a coherent visual presence across one or more eligible screens.
Operator workflow
- Create a takeover with a clear internal title.
- Select the eligible display destinations.
- Upload only media approved for public venue use.
- Review the isolated preview and disable anything that should not play.
- Choose a bounded end time, then deliberately publish.
- Stop it early if the event ends or the content is no longer appropriate.
Previewing is not publishing. A draft remains off the live screens until an authorized operator explicitly starts it.
flowchart LR DRAFT["Draft media"] --> PREVIEW["Review and preview"] PREVIEW --> START["Authorized start"] START --> LIVE["Selected venue displays"] LIVE --> STOP["Manual stop or automatic expiry"] STOP --> NORMAL["Normal programming resumes"]
Safety guarantees
- Every takeover has an end time and stops automatically.
- Starting, editing, and stopping require Pub permissions.
- Media preparation failures do not bypass preview or enter the live rotation.
- A change made from stale operator state is rejected for review rather than silently overwriting a newer change.
- Normal display programming remains available to resume after the takeover.
Content guidance
Use legible, high-contrast images and short videos that work without sound. Confirm consent and usage rights for every person, logo, and artwork shown. Avoid small text, rapid flashing, private attendee information, and media that depends on a precise screen arrangement.
Technical boundary
The product keeps draft, preview, and live state separate. Published state contains only the approved media selection, destinations, and bounded lifetime needed by the display system. Exact upload limits, storage layout, screen identifiers, and control protocol remain private operational details.
Related: Venue displays · Admin access