The same edit, repeated per site
A price change is one decision followed by dozens of identical actions: open the branch, find the screen, upload the file again. Publishing to a location makes it one action.
Have an idea for Veysign? Suggest a feature or improvement →
Multi-site operations
Changing signage across multiple sites is one decision followed by a visit to every branch, unless the screens are managed centrally. Veysign gives that operator one dashboard: publish a playlist to the locations it applies to, then confirm it landed.
Why teams change the workflow
A price change is one decision followed by dozens of identical actions: open the branch, find the screen, upload the file again. Publishing to a location makes it one action.
One branch has different hours or a local promotion. Schedules rank by priority first, then by how specific the target is, so an exception sits over the wider campaign without removing it.
A screen behind a failed router, or one switched to the wrong input, never takes the update, and the campaign plan does not show that. Device status and last contact do.
Implementation
Create the location, then install the Veysign player from Google Play on Android 9 or newer. An owner or administrator enters the six-digit code the player shows, which pairs the screen to the organization, then moves it to its location from the screen list.
A device group is organization-wide rather than tied to a site, so it can hold every front counter or waiting room in the estate. Group by what decides the content, not by geography.
Point the schedule at a location or a group, then set its days, times, dates, and priority. One publish covers every screen in that target, including screens added later.
Open the screen list and check status, last contact, and the current assignment. An offline player applies the change when it reconnects, so chase the screens that stay out of contact.
Product fit
Plans are limited by screens, storage, and team members, never by the number of locations. Locations are unlimited on every tier including Free, so a new site costs nothing until screens go into it.
Assign content to a single screen, a group that spans sites, or a whole location. Where schedules overlap, priority is read first, and the more specific target wins when priorities match.
A schedule carries its own timezone, so a campaign set for 08:00 starts at 08:00 in the timezone that schedule names, not wherever head office sits. A region on its own clock needs its own schedule.
With no schedule active, a screen falls back to its own assignment, then to the default playlist on its location. A new site shows approved content before anyone builds its schedule.
Size the plan from screens, not from addresses. Twenty screens across six branches is the same twenty screens as twenty in one building: the Business plan, $39 a month or $390 a year, an annual term priced at ten months. Above fifty screens is Enterprise. Prices are in USD and exclude sales tax or VAT.
Name screens so an operations person can act on the name alone: site, area, and orientation carry more than TV 1 and TV 2. Set the organization device PIN before the players leave the office, since it reaches every paired screen on the next sync and keeps branch staff out of the player settings.
Decide which layer owns what before exceptions arrive: a default playlist per location as the floor, group schedules for central campaigns, a device override where a branch differs. An administrator manages screens and locations, a content manager builds media, playlists, and schedules but cannot unlink a device, and a viewer reads only. No role is scoped to one branch, so site ownership stays an operating agreement.
Assign screens to locations and groups, then publish to that target instead of to each screen. Every player under it applies the change on its next check in, including screens added later.
No. Locations are unlimited on every plan, including Free. Plans are limited by screens, storage, and team members, so a new site costs nothing by itself; only the screens installed there count against the plan.
Yes. Publish the shared content to a group or a location, then add a schedule on the site or screen that differs. Priority is read first, and the more specific target wins when priorities match, so give the exception the higher priority and it takes over on those screens without removing the wider campaign.
Owners and administrators are emailed when a screen stops checking in, unless the organization turns those alerts off. The screen list also shows status, last contact, and the assignment each player should be running.