Getting started.
WeDisplay runs three products from one account and one bill: digital signage on the screens you own, a visitor kiosk for your reception desk, and an ad marketplace for selling screen time on the screens you already run. This page is the short version — the full manual lives inside the app under Documentation once you are signed in, and it goes into far more detail.
Quick start: your first signage screen
1. Create your account
Sign up and you are signed in straight away — there is no confirmation e-mail to wait for. If you chose a plan on the pricing page first, you land on Billing with that plan ready; otherwise you land on Screens, which is where the next four steps happen.
2. Install the player on your device
Open Screens → Install a Player and pick the hardware you have. Android TV, Google TV and Android boxes: open the address the dialog shows in the TV's browser and install the app. Windows: one PowerShell line. Raspberry Pi: one shell line. Samsung business TVs run Player Lite, the lightweight player built for smart TVs. Any browser works too and is the quickest way to try things out — but the installers survive a restart, so use one of those for a screen nobody watches over.
3. Pair the screen
The device shows a six-digit code as soon as the player starts. Back in the dashboard, go to Screens → Add Screen, type the code in and give the screen a name. If no code appears on the device, follow the “Don't have a code?” link in that dialog — it means the player is not installed there yet.
4. Upload media and build a playlist
In the Media Library, upload the photos, videos, PDFs and slide decks you want to show. Then open Playlists, create one, add those items and set how long each of them stays on screen.
5. Assign the playlist
Go back to Screens and assign the playlist to the screen, or to a whole group of screens at once. The player picks up the change and starts playing within seconds — nothing to restart, nobody to send over to the TV.
Content
The Media Library holds everything you play. It accepts photos and graphics, including SVG; videos, including the MOV files a phone or a camera produces; PDFs; and PowerPoint, Word and Excel documents. Spreadsheets saved as CSV go in separately, as Datasets, and feed live tables on screen. Every upload is checked on arrival: the contents have to match the file type, not just the file name.
Playlists put items in order and give each one a duration. Layouts split a single screen into zones, so a video, a headline and a live widget can share it. Schedules decide when a playlist or a layout is on air — start and end dates, times of day, days of the week — and the player switches by itself.
Video Walls tile one picture across several screens that behave as one. Widgets add live data to a zone: clock, weather, news ticker, countdown, QR code, calendar, or a table drawn from one of your Datasets. Sources send something live to a screen in real time — a browser tab, a camera, a meeting room or a desktop — with nothing to upload first.
Proof of Play reports say what actually ran, on which screen, when, and for how long, and export to PDF or CSV.
Uploaded files are never left sitting in a public folder. They are served through the application's own media route, which only hands back files registered to your organization, and every media link carries a per-file signature.
Screen pairing
Pairing goes one way: the screen shows a number, you type it into the dashboard. A player that has not been paired yet asks the server for a code every few seconds and shows whichever one it is given, so the number on the TV is always a current one. There is no countdown to beat and nothing to refresh — which matters, because on a TV appliance there is no page to refresh.
In the dashboard, Screens → Add Screen takes that code plus a name for the screen. The screen joins your organization, the player notices within a few seconds, and it starts showing whatever you assigned to it.
If no code ever appears on the device, the player is not installed on it yet: go back to Screens → Install a Player and run the installer for that hardware. A screen that was never paired and has not been heard from for seven days is tidied away automatically — there is nothing to undo, because the device registers itself again and shows a fresh code the next time the player starts.
The other two products
Visitor kiosk
A tablet or a screen at reception becomes a sign-in desk: visitors check themselves in, the person they came to see is notified, badges print, and the documents you require are signed and kept. Read about the visitor kiosk.
Ad marketplace
Sell screen time on the screens you already run: advertisers, campaigns, day-parts, and a report per campaign showing exactly what played, where, and for how long. Read about the ad marketplace.
Integrations and API
The routes under /api belong to the dashboard itself and authenticate with your signed-in session. There is no public API token today, so a script cannot call them on your behalf. What is available for automation:
Directory sync and single sign-on
SCIM 2.0 provisioning creates, updates and removes accounts straight from your identity provider, and SAML 2.0 or OIDC signs your team in with the credentials they already use. Available on plans that include them; our page on security and identity has the detail.
Offline alerts by webhook
Give your organization a URL and WeDisplay posts to it when a screen has been quiet for longer than the threshold you set, then posts again when it comes back. An e-mail address works the same way.
Player install scripts
The Windows and Raspberry Pi installers are single-line scripts, so a new screen can be prepared by your own imaging or fleet tooling and arrive already showing a pairing code.
Everything else happens in the dashboard. See what the platform does, or open Documentation once you are signed in.