Most digital signage tenants I inherit are not under-organized. They are organized three times over.
I spend most of my time inside other people’s digital signage deployments. Enterprise fleets, a few hundred to a few thousand screens, usually mid-migration off a platform that stopped keeping up. The tenants that have gone sideways almost never got there through neglect. They got there because someone smart built a structure that worked at forty screens and kept extending it well past the point where it still made sense.
The failure is always the same shape. One organizing system was asked to answer more than one question.
Korbyt hands you three separate handles: Media Manager folders, player groups and player metadata, and tags. Clicking around, they look interchangeable. They are not. Each one answers a different question, and the moment you make one of them do double duty, you inherit a maintenance problem you will feel in about eighteen months.
The short version: what folders, players, and tags each answer
- Media Manager folders answer what the content is and who owns it. Permissions live here.
- Player names, player groups, and player metadata answer where the content plays.
- Tags answer which moment the content runs in. Lock tag creation on day one so users can only apply the tags that you approved.
Media Manager folders answer what the content is and who owns it
Media Manager folders are the content axis. What is this asset, which bucket does it belong to, and which team is allowed to touch it?
A media and communications company I worked with had a library that divided content into four categories across four different places. By access in one branch, by content type in another, by campaign in a third. Every one of those calls was defensible on the day it was made. Together they meant nobody could answer where a new file should go without asking somebody.
We collapsed it into one tree where the top level answers scope and the second level answers audience. Numeric prefixes so it sorts on purpose instead of alphabetically: 00 for brand templates and fallback images, 01 for content that goes everywhere, then headquarters, corporate offices, regions, campaigns, and a 99-Archive at the bottom. Boring by design.
The real reason to protect folders as the content axis is permissions. Folder permissions let a tenant administrator restrict a folder and its contents to specific CMS user groups, and Korbyt then offers to push the same permissions down through every subfolder underneath. That is the cleanest access control in the platform, and it only works if your folder tree matches how your teams are actually divided. Organize folders by campaign and your permissions have nowhere to live. Explore Using the Media Manager to learn more.
Player groups and metadata answer where the content plays
The placement axis lives on the device side, in the player name and the metadata attached to it.
Start with the naming convention and treat it as load-bearing rather than cosmetic. A pattern like BusinessUnit-Site-Group-Sequence gives you a queryable string. Group rules support contains, starts with, ends with, is, is not, and empty checks, which turns every segment of that name into a targeting handle. One rule matching “contains Elevators” picks up elevator screens across two buildings, and nobody has to maintain a list.
Player metadata does the rest. Orientation, screen class, audience. Those are the conditions your Clever Rules evaluate when deciding whether a given asset is allowed on a given screen. Keeping 4K content off a 13-inch elevator panel is a metadata problem, not a folder problem.
Groups also stack, which people underuse. A player can sit in a global group, a country group, a region group, a site group, and a space-type group simultaneously, and playlists stack against each other the same way. That layering is how enterprise-wide content and location-specific content share one screen without fighting.
The retail bank I am working with now runs close to 4,000 players across roughly 1,000 fully digital branches. At that size, the naming convention is the whole difference between writing rules once and maintaining a spreadsheet forever.
Tags answer which moment the content runs in
Tags are the third axis. My honest recommendation is to use them least and lock them hardest.
They are good at exactly the thing folders and player names are bad at: cutting across the tree for a campaign or a season. Open enrollment content that lives in four departmental folders and needs to go live on one date is a tag, not a folder.
What tags are bad at is being an accident. By default Korbyt lets anyone type any tag they want, and free text plus a dozen content contributors reliably produces a shadow taxonomy that nobody designed and nobody can audit. You can prevent this. Tag creation can be locked so that only tenant administrators and administrators create tags, after which everyone else picks from a dropdown instead of typing. Tagging in Korbyt.
One exception worth naming, because it cuts against my own advice. A community college system I worked with went deliberately tag-first, and it collapsed more than forty playlists into four. That works. It works because they locked tag creation on day one and treated the tag list as a controlled vocabulary rather than a suggestion field.
Which is why I recommend locking tag creation even for customers whose architecture does not depend on tags at all. It costs nothing this week and it stops someone from quietly rebuilding a parallel structure eighteen months from now.
The test: which question is each system answering?
Take one content routing rule you already have in production and say out loud which of the three questions each part of it answers. Content, placement, or moment. If any single handle is answering two of them, that is where your next problem is coming from.
Worth doing before you provision the next hundred players, not after.
FAQs
Answers to common questions about managing media, screens, and tags in Korbyt.
Not for scheduling. A campaign branch is fine for storing the assets, and the tree above has one. But campaign activation cuts across the tree, which makes it a tag job. Folders carry permissions, so the shape of the tree has to match how your teams are divided, not how your calendar is.
Put the targeting information in the player name and let group rules do the work. Rules support contains, starts with, ends with, is, is not, and empty checks, so one rule can pick up every elevator screen across two buildings.
Restrict tag creation to tenant administrators and administrators. Everyone else then picks from a dropdown, which keeps the tag list clean and controlled.
