An International Radio Ministry Runs Multi-Language Production on One Files.com Platform

An international radio ministry has been on the air for decades, producing audio and video devotionals that broadcast partners air in countries around the world. The reach is deliberate: the ministry aims its programming at the places conventional missions cannot go, including warzones, refugee camps, and regions where the native church is small or absent.

Reaching those listeners means reaching them in their own language, and the ministry does not translate in-house. English scripts and audio masters go out to regional production partners across Africa, Eurasia and Central Asia, and Europe. Each partner translates, records, and produces a local-language version, then sends the finished program back. The ministry then distributes that programming to the radio stations and networks that air it.

Nothing the ministry makes reaches a listener until it has left the building, been remade by an outside organization, and come home again. That round-trip is the ministry's entire supply chain, and it used to run by hand.

With Files.com as the hub, the ministry replaced a hand-carried exchange with a loop that partners and stations drive themselves. Dozens of languages are in active translation at once, with several media assets in simultaneous multi-language production, all on one platform.

The Middleman Was the Security Model

The library of .wav audio masters and English scripts lived on an on-premises server, and files moved when someone at the ministry moved them, using desktop transfer tools such as Cyberduck. Every outbound script, every returning translation, every program delivered to a station passed through a manual hand-off.

The obvious fix, giving partners direct access, was the dangerous one. A translation partner cannot deliver finished work without write access, and unscoped write access to a shared library is the ability to damage it: overwrite a master, or delete another language's finished programs. With regional partner organizations on three continents, some producing ten or more languages each, an open server would have put every partner one mistaken upload away from another partner's work. Hand-carrying the files was slow, but it was also the access control. The bottleneck and the security model were the same person.

The ministry was adding languages and putting multiple media assets into production at once, with a stated goal of reaching a triple-digit language count within two years. A roster that size cannot pass through a manual desktop hand-off.

What replaced the manual exchange had to do several things at once. It had to give every partner and station direct access from anywhere in the world, over a browser or a standard SFTP client. It had to show each partner only the languages it owns, with write access scoped to exactly those folders. It had to split the largest partners further, so an organization producing ten languages holds region-specific credentials rather than one master key. And it had to keep an archival copy current without anyone maintaining it. The ministry selected Files.com to be that hub.

One English Source Folder, a Folder for Every Language

The library came off the on-premises server, and Files.com became the primary repository. A Files.com remote server sync now pushes everything to SharePoint, so the archival copy maintains itself.

The round-trip runs through a single structure. English masters and scripts sit in one curated source folder that every production partner can download from. Each language has its own folder, and a partner uploads finished productions into the folders for its languages and nowhere else. Radio stations and networks log in and pull finished programming straight down to their own systems.

Files.com user groups and folder-level permissions are what make that structure safe to open up. The ministry's media services director built the groups and permissions himself: each translation partner is scoped to see and write only its own language folders, and the largest partners are segmented by region, so a ten-language organization holds several narrow logins instead of one broad one.

Partners and Stations Drive the Loop

• Partners and stations read thousands of files a day from the platform. Because they pull those files themselves, nobody at the ministry pushes a single one of them.
• A partner uploading a finished translation can touch only its own language folders, so an accident is contained to the work that partner already owns and can never reach another language or another partner.
• Adding a language is a folder and a permission, and adding a partner is a scoped login. The stated path from dozens of languages toward triple digits asks for no new infrastructure and no new staff.

Designing Access Instead of Carrying Files

The director's work is designing access rather than carrying files: partners take the English masters, return the translations, and stations collect the finished programs, each inside a boundary that makes the mistake they might have made impossible.

A ministry built to speak to people in their heart language found that a many-to-many translation loop did not need a bigger team. It needed each partner's write access scoped to exactly the folders that partner owns, and Files.com is where that boundary is drawn.