Airlite Plastics Moved External Sharing from Email, OneDrive, and SharePoint to Per-Partner Files.com Spaces

Airlite Plastics is an Omaha, Nebraska-headquartered plastics manufacturer producing rigid packaging containers for consumer brands and building products.

That business model has a consequence for files. The artwork on a container belongs to the brand customer, and it travels back and forth as design files long before anything is molded. The machinery that does the molding comes largely from equipment builders in Western Europe, whose schematics and specifications travel the same way. Airlite's most sensitive files all have somebody outside the company on the other end.

Internal collaboration stays on the Microsoft stack, where it works well. Files.com is the edge: the moment a file has an outside party on the other end, it moves there.

Container Artwork by Email, Large Machine Designs Too

For years, that exchange ran on email. The graphics team traded container artwork with brand customers as attachments, which was neither secure nor practical for large design files. Engineering had the same problem at a larger scale, exchanging designs with the overseas builders of its presses and molds.

The obvious alternative was already in the building. Airlite ran OneDrive and SharePoint for internal collaboration, and users reached for them when a file had to go outside. That is where the second problem lived.

A Correct Share Depended on Whoever Created It

An external share on the Microsoft stack depended on the person who configured it. Users had to set its scope and safeguards correctly, and controlling external sharing from the user's endpoint proved difficult in practice.

That put IT in a position no IT team wants: either inspect every share a designer or engineer created or rely on each user to configure it correctly.

The structure of the problem made it hard to fix from the center. Every packaging customer is a separate company. Every machine builder is another one. IT could not sit in the middle of every exchange, and a tool that required IT to configure each share would simply have been routed around. Whatever replaced email had to be something an ordinary user could operate correctly, unaided, and it had to produce a contained result every time.

Airlite selected Files.com to be that route for anything leaving the company.

A Files.com Space per Customer, a Root Folder per Partner

What Airlite built on Files.com was a single external edge where the contained configuration was the one users produced by default.

Each packaging customer and each equipment builder received a dedicated space. Each external party received a Files.com user whose root folder was set to that space. When partners log in, they land directly in their own folder and never see the wider structure. Users do not have to set the scope for each exchange because it is a property of the account itself. And Airlite's own users can create these partner accounts and spaces themselves, without a ticket.

“When they go in they don't even see the folder structure, they just land right there.”

The Easier Path Became the Governed One

With Files.com carrying the external exchange, Airlite replaced email attachments and user-configured cloud links with a pattern that comes out contained every time.

Users route external files through Files.com because it is the simpler path, not because a policy tells them to. Every new brand customer and machine builder inherits the same contained pattern without IT enforcing it exchange by exchange.

Today, a designer sending artwork to a brand customer or an engineer trading designs with a builder in Western Europe reaches for Files.com first. Internal work remains in OneDrive and SharePoint; external work moves through a Files.com account scoped to one counterparty.

That is the lesson in Airlite's story. External sharing became governed not by asking users to configure every link correctly, but because Files.com made the contained share the easiest one to create—and the easiest path is the one people take.