City of Midland Restores Plan-File Access With a Files.com Custom Domain—No Partner Firewall Changes Required

The City of Midland is the municipal government at the heart of the Permian Basin, serving one of the fastest-growing cities in the United States. More than 130,000 people live there, the economy runs on energy, and the construction pace matches both. Growth on that scale produces a steady stream of plan documents: road projects, subdivisions, and utility work in the right-of-way, each coordinated between the city's Engineering department and the private companies doing the work.

That roster of private companies is long by design. Utility services in Midland come from a range of separate providers operating under franchise agreements, alongside the contractors the city hires directly. Engineering's daily work therefore depends on exchanging files with organizations whose networks the city does not run, cannot see into, and has no standing to change. That last fact is where the problem started.

Plan Documents Stopped at the Partner's Firewall

Several of the city's counterparties, including national telecommunications carriers among its franchise utilities, run locked-down corporate networks. Their web filters block external file-sharing destinations as a category. The filter is not blocking one tool or one link; it blocks the entire category, including the login page. When Engineering tried to share files with one of those carriers, nothing on the other end would load. The share page was blocked. The download was blocked. The recipient could not even reach a sign-in screen.

The cost landed at the worst possible point in the work. A utility working against city plans for road, subdivision, or right-of-way work was waiting on documents that Engineering had ready and could not deliver. And there was no one to call. The block lived in the counterparty's filtering policy, applied automatically by a system whose administrators had never heard of Midland's project and were never going to make an exception for a file-sharing URL.

The diagnosis underneath the incidents was uncomfortable: any file exchange served from a shared vendor domain is at the mercy of every partner's filtering rules. A corporate web filter does not evaluate the file or the sender. It evaluates the domain. A domain shared by thousands of organizations gets categorized once, as file sharing, and blocked wholesale, and every customer of that vendor is blocked along with it.

A Fix That Could Ask Nothing of the Counterparties

The obvious fixes were unavailable. The city could not ask a national carrier to change its firewall rules, and it could not run exception requests through the IT department of every contractor and utility it works with. That would be a negotiation per partner, repeated every time the roster grows. Whatever the city did had to work inside one constraint: it could change nothing on the recipient's side. The fix had to change what the recipient's filter saw.

That set the requirements. File delivery had to come from an address that reads as the City of Midland, not as a file-sharing service. Recipients had to need nothing on their end: no software, no account, no ticket to their own IT. Links carrying plan documents had to expire on their own rather than sit open indefinitely. And the same approach had to cover both directed delivery, a link sent to one contractor, and open retrieval, published plan sets a contractor pulls down on their own schedule.

Midland runs its external file exchange on Files.com, and the answer to exactly this problem is the Files.com Custom Domain: the whole exchange served from a domain the city owns.

Every Link Served From the City's Own Domain

The city put its Files.com site behind a custom domain carrying the city's own name, with the SSL certificate provided and managed by Files.com. That one change moves every surface a counterparty touches. The login page, the share pages, the download links: all of it serves from a city-owned address. To a partner's web filter, the destination is a municipal government, not a categorized file-sharing platform.

On top of that domain, Engineering delivers plan documents two ways. For directed delivery, staff send Files.com Share Links. The contractor clicks, the page opens in any browser, and no account is required on their end. Links expire after 30 days by default, so a plan set cannot stay downloadable long after the job that needed it. For standing distribution, the city uses Files.com Public Hosting: folders of plan documents served at stable web addresses that contractors retrieve on their own, with no one at the city handling each request.

The custom domain is the piece that makes the rest reachable. Share Links and hosted folders are useless to a recipient whose filter kills the page before it loads. Served under the city's name, they load.

Blocked Twice, Restored Twice, With No Firewall Requests

With delivery served from its own domain, the city replaced a path that any partner's filter could switch off with one the city controls end to end. The results showed up immediately, and then again in 2026.

• Engineering now shares plan documents directly with the national carriers whose networks had blocked the exchange outright, including the login page. Access was restored by the domain change alone; no carrier altered a firewall rule.
• When contractors' filters later blocked the shared web address the platform uses for publicly hosted files, in 2026, the same fix applied. The city served those hosted plan files from its own domain and contractor access came back, again with nothing asked of any contractor.

Plan Delivery Back Under Midland's Control

Today, the engineer sends the link and the work moves, because the destination carries the city's name and a browser is all the recipient needs.

The lesson travels well beyond Midland. Any organization whose counterparties run locked-down networks is one filter update away from the same stalled exchange, whichever file-sharing platform it uses, because the filter judges the platform's domain rather than the files. The city runs its exchange on Files.com and serves every link from a domain it owns, and no partner's web filter gets a vote on whether its files arrive.