A Radio Broadcaster Feeds Broadcast Automation From Files.com Mounted as a Network Drive

A national radio broadcaster operates dozens of stations across more than a dozen major markets, alongside television and digital properties.

Radio at that scale is a production business, and production runs on files. Commercials, mixes, produced segments, and songs are made by people in one market and have to reach another market's air chain the same day. The last step is always the same: a producer or on-air talent drops finished audio into a folder, and the station's broadcast automation picks it up, assigns it a cart number, and queues it for playback. Wide Orbit, the broadcast automation at the end of that chain, collects those files only through a mapped network drive. The file layer between those two steps is effectively part of the air chain. When it fails, what fails is getting content on the air.

A File Layer Held to the Standard of the Air Chain

For about two years, that layer was Microsoft OneDrive, with a shared folder per market. A desktop sync client is an uneasy fit for an air chain: when a sync did not complete, the fix was a user reboot and a service call to engineering, who then spent their time troubleshooting someone's desktop client instead of running stations.

The broadcaster wanted the file layer held to the same standard as the rest of the chain. Every action on a market's content had to trace to a named person from the corporate directory. Each market's content had to stay segmented from the others. And a production workforce that turns over continuously had to be absorbed without hand-built accounts.

The Broadcast Automation Only Connects Through a Mapped Drive

The constraint on any replacement sat at the end of the chain.

Wide Orbit, the broadcast automation that collects files after production staff drop them, connects to storage only through a mapped network drive. Whatever replaced OneDrive had to present itself as a drive letter on the machines Wide Orbit watches. That requirement rules out most cloud sharing tools, which reach the desktop through the same kind of sync client the broadcaster wanted out of the chain.

The second constraint was the workforce. The population touching these folders is well over a hundred production staff and on-air talent across the markets, and it turns over continuously. Managing that many accounts by hand, and tying each of them to the company's Okta identity and MFA, had been a standing burden of its own.

So the replacement had a specification before it had a name: present as a mapped drive to the broadcast automation, give every person an individual identity from the corporate directory, keep each market's content segmented, and absorb constant turnover without per-user setup. The broadcaster selected Files.com to be that layer.

A Folder Per Market, Presented as the Drive Wide Orbit Expects

The structure on Files.com is simple. Each market has its own folder, with access granted through group-based permissions rather than per-user grants. Internal users sign in through the broadcaster's Okta SSO integration over SAML, so every action belongs to a named individual, and access follows the identity the company already manages.

On the machines feeding broadcast automation, Files.com is mounted as a network drive. Wide Orbit picks files up from a mapped drive exactly as it has for years; the software was never modified or reconfigured. Only what stands behind the drive letter changed.

The rollout started in three smaller markets and then extended across the rest of the footprint, market by market, on the same pattern.

Every File Now Carries a Name, a Time, and a Machine

With Files.com in production as the file-sharing layer, the broadcaster changed the operating model:

• Access runs on individual Okta identities, so every action traces to a named person, and a population that turns over continuously is managed through group membership rather than hand-built accounts.
• The desktop sync client, and the reboots and service calls behind it, left with OneDrive. Engineering stopped being the help desk for the file layer.
• Wide Orbit ingests from the same mapped drive it always has. The broadcast automation was never touched.

There is a compounding result behind the immediate ones: the pattern repeats. Standing up the next market is a folder, a group, and the same mounted drive, which is how the deployment spread across the company on one design instead of one per market.

The Broadcast Automation Never Had to Change

Today, when a commercial isn't where it belongs, an engineer at the broadcaster reads a log entry that names a person, a time, and a machine, and the question is answered before anyone reboots a desktop.

The constraint that appeared to lock the broadcaster into its existing file layer turned out to constrain only the interface. Wide Orbit still sees the mapped network drive it requires; behind it now runs Files.com, with individual identity, per-market permissions, and a full record of everything that touches the air chain. An application that only accepts a drive letter did not dictate what stood behind the letter. It only dictated how the modern platform had to present itself.