Every site's screens, one login, nobody on a ladder.
Running screens for five sites is not five times the work of running one, if the account is built for it. Here is how an organisation with several venues is laid out, and what changes between Growth and Venue Pro.
The shape of it
An organisation is the account. On Growth and above it holds several venues. Each venue has its own timezone, its own screens, its own playlists and schedules. A screen belongs to one venue and can be moved to another from the admin without re-pairing it.
Who sees what
Team invites and roles are on every plan: owners, admins, editors and viewers. Editors can be scoped to the venue they work on, so the manager in one city changes that city's boards and nothing else. Head office keeps an owner account that sees everything.
Getting thirty TVs paired without thirty visits
A single screen is paired by reading a six-character code off the TV and entering it in the admin. For a fleet, Venue Pro adds bulk provisioning: generate tokens in advance, send each site a link, and the TV at that site pairs itself to the right venue with the right name when someone opens the player on it.

Content that is shared, and content that is not
Playlists and media belong to the organisation, so a brand card is made once and scheduled at every venue. Each venue's schedules are its own, so the same card can run at 17:00 in one city and 18:00 in another, and local specials stay local.
Approvals, when you need them
Venue Pro adds approval workflows. A client's slide, or a site manager's, goes live only once someone with the right role has signed it off. On Growth there are no approvals and nobody waits; choose based on how many hands are on the content.
Reporting across the fleet
Every play is logged per screen on every plan. On Growth and above the proof-of-play report runs by screen and date range, and QR scan counts are per screen, so a report for one client or one region is the same report filtered to their screens.
Encoding at scale
Every upload is re-encoded before it reaches a screen. Venue Pro gets a priority encoding queue, so a fleet's uploads do not wait behind everyone else's.