Skip to main content

October 2026

October 2026 adds two public resources for security and compliance reviews: a Security Reference that explains how the platform behaves, and an expanded Compliance reference with assurance documents you can request through the Trust Center. We also shipped security updates to installed Files.com software, so update any installation that doesn't update itself.

The Desktop App now runs on Linux, and on Windows a mounted drive can open a large file without downloading all of it first. Python SDK 2.0 and .NET SDK 2.0 build parallel transfers and checkpoint recovery into the SDK, and a new PowerShell module brings Files.com administration to Windows scripts. If you manage Files.com with Terraform, start moving JSON-valued settings to native HCL before the provider's next major release.

Security Updates for the Agent, Desktop App, CLI App, Mobile App, and MuleSoft Connector

We shipped security updates in October to the Files.com Agent, the Desktop App, the CLI App, the Mobile App, and the Files.com Connector for MuleSoft. If you run any of them, update to the latest version.

The Agent and the Desktop App update themselves by default. If your team turned off automatic updates to manage deployment itself, install the new versions now. The Mobile App updates through the App Store and Google Play, so keep store updates on for the devices you manage.

Install the latest MuleSoft connector from Maven Central, where new connector versions are published before they reach Anypoint Exchange. The connector installation guideExternal LinkThis link leads to an external website and will open in a new tab shows the dependency to add.

Learn more about Client Software and Security Updates.

Security and Compliance Resources

Security reviews and vendor assessments now have two public references to work from.

Security Reference

The new Security Reference explains how the platform behaves across authentication, administration, access control, encryption, and automation, why we designed it that way, and what each configuration choice means for your site. Administrators, integration developers, and security teams can use it to decide what to run on Files.com, how to configure a site, and how to connect it to other systems.

It is also the specification for independent security testing. If your team or a testing firm plans an assessment of Files.com, give them the Security Reference before they plan tests, and review each finding against it. Testing still requires approval and advance coordination, as described in Planning a Security Assessment.

Compliance Reference and Trust Center

The Compliance reference now goes much deeper on how we operate the company, the commitments we make, the responsibilities that stay with you, and the independent assurance behind each claim. Audits & Assurance matches common review requirements to the evidence that answers them.

The Trust CenterExternal LinkThis link leads to an external website and will open in a new tab carries the assurance documents reviewers ask for most, including our SOC 2 Type II report and bridge letter, completed CAIQ, PCI Attestation of Compliance, penetration test completion letters, and VPAT. Browse the catalog without an account and request a document directly from it, instead of asking your account team. Our security team reviews each request, and these documents require a signed NDA.

If you renew vendor assessments or compliance certifications on a regular cycle, start each renewal at the Trust Center. Use Reclaim access to restore access granted for an earlier review. Document Requests explains eligibility and access.

Desktop App Updates

Desktop App for Linux

The Desktop App now runs on Linux, with Turbo Transfer Mode, Sync Mode, and Mounted Drive Mode, and the same browser sign-in, including SSO. Linux workstations can now use the same app as the Windows and Mac machines on your team, with each connection mounted as a folder at ~/Files.com/<connection name>.

Installing on Linux has .deb packages for Ubuntu and Debian and .rpm packages for Fedora, for Intel/AMD and ARM 64-bit, along with the supported releases. Install the package once. It adds the Files.com repository, and later versions arrive through apt or dnf with the rest of your system updates.

The app doesn't update itself on Linux. To control which version runs, an administrator disables the Files.com repository and distributes approved updates.

Partial Downloads for Windows Mounted Drives

A Windows mounted drive can now download only the parts of a file an application reads. A media player can open a large video and seek within it, and an archive tool can list a ZIP file's contents, without waiting for everything before the part it needs. Reading a whole file from start to finish takes about the same time as before.

Partial Downloads is on for new installations. On an existing installation, opt in under Settings > Caching; Files.com will gradually enable it for all Windows mounted-drive users. It doesn't apply on macOS, where Finder access goes through Apple's File Provider.

Python and .NET SDK 2.0

Version 2.0 of the Python and .NET SDKs builds parallel transfers, folder jobs, and checkpoint recovery into the SDK, so an integration needs less of its own scheduling and retry code. Both are major upgrades with breaking changes, so review the migration guide before moving an existing integration.

Python SDK 2.0

Python SDK 2.0 sends upload parts in parallel and adjusts concurrency to the connection. upload_directory(), download_directory(), upload_files(), and download_files() move many files under shared limits and report each file's outcome. Each files_sdk.Client keeps its own credentials and settings, so one script can work with several accounts or Workspaces.

A transfer given a checkpoint can resume after an interruption and reuse the work already completed, under the conditions in Pausing and ResumingExternal LinkThis link leads to an external website and will open in a new tab. download_file() writes to a temporary file first, so a failed download leaves the existing local file in place. UploadsExternal LinkThis link leads to an external website and will open in a new tab and Directories and Many FilesExternal LinkThis link leads to an external website and will open in a new tab have examples.

Version 2 requires Python 3.11 or newer. Review the migration guideExternal LinkThis link leads to an external website and will open in a new tab before upgrading an existing integration, and pin Files.com<2 to stay on 1.x until you have.

.NET SDK 2.0

The new client.Transfers methodsExternal LinkThis link leads to an external website and will open in a new tab in .NET SDK 2.0 tune the number of parallel parts to measured throughput, transfer whole folders, report progress, and resume from a checkpoint without resending completed work. DownloadFileAsync puts a file in place only after every byte has arrived and passed validation.

The existing client.RemoteFiles helpers remain available and still send upload parts one at a time, so an integration gets these capabilities by moving to client.Transfers. Version 2.0 supports .NET 10, .NET 8, and .NET Framework 4.8 and 4.8.1; test a .NET Framework application with 2.0 before you deploy the upgrade. Review the migration guideExternal LinkThis link leads to an external website and will open in a new tab before upgrading.

PowerShell Module for Windows Administrators

FilesCom.PowerShell is a new module that runs Files.com administration as native PowerShell commands. List commands return objects you can filter and pass to the next command, so an access report or a group membership change takes a short pipeline instead of API requests and JSON handling.

The administration and reporting guideExternal LinkThis link leads to an external website and will open in a new tab covers exporting users, group memberships, and folder permissions to CSV, provisioning users and permissions from a CSV after previewing the changes with -WhatIf, and changing group memberships. Unattended scripts run from Windows Task Scheduler or your job runner, with the API key kept in a secret vault, as described in Automation and Scheduled JobsExternal LinkThis link leads to an external website and will open in a new tab.

The module requires PowerShell 7.4 or later on Windows; Windows PowerShell 5.1 isn't supported. InstallationExternal LinkThis link leads to an external website and will open in a new tab explains how to install it from NuGet.org.

Native HCL for JSON-Valued Settings in Terraform

The Files.com Terraform provider now accepts native HCL objects for settings the API stores as JSON, such as folder behavior values, Event Target configuration, and Child Site Management Policy values. The provider documentationExternal LinkThis link leads to an external website and will open in a new tab describes each field, so these settings read like the rest of your configuration instead of as encoded strings.

Configurations that still pass JSON strings keep working and produce a deprecation warning. A major provider release planned for March 1, 2027 makes these settings typed objects and stops accepting the older formats, so move your configurations over before you upgrade to it.

One change needs attention when you upgrade now: Event Target config and Child Site Management Policy value are marked sensitive, so a root module output that returns either one needs sensitive = true. The provider's upgrade notes cover this and the other changes.

Customer-Managed KMS Keys for Amazon S3 Remote Servers

Files.com can now write to Amazon S3 buckets whose policy requires every write to name a specific AWS KMS key. Enter the key's full ARN in the new KMS Key ARN setting on an Amazon S3 Remote Server, and Files.com encrypts the objects it writes with SSE-KMS under that key, through Remote Server Mounts, Syncs, and Direct Routing alike. Key IDs and aliases aren't accepted.

The connection's IAM user or role also needs kms:GenerateDataKey and kms:Decrypt on the key. Changing or clearing the setting affects later writes only; existing objects keep their encryption.

PFX and P12 Certificate Import for AS2

AS2 identities and trading partners now accept a PKCS#12 file (.pfx or .p12) directly, so a certificate that arrived as a PFX file no longer needs converting to PEM first. Choose Import PKCS#12 File (PFX or P12) under Certificate Source and enter the file's password, if it has one.

For your AS2 identity, the file must contain your certificate and its matching private key. For a trading partner, Files.com needs only the public certificate and discards any private key the file includes.

AS2 Message Details and Replay

When an incoming AS2 file fails to deliver, or a downstream system loses or mishandles it, you can now process the retained message again without asking your trading partner to resend it. Open the message from the incoming AS2 log and select Replay Message. Files.com processes the original content with your current AS2 configuration and records the result as a new attempt, leaving the original record in place.

Each incoming message now has its own details page with its status, AS2 Message-ID, file and MDN contents, and the result of each processing step, so you can find where delivery failed and fix the cause before replaying. Site Administrators and administrators of the message's Workspace can replay any message still within the retention period.

A replay can deliver the file again and repeat the receiving folder's processing. Confirm your downstream workflow is ready for another delivery, as described in Replaying Incoming Messages.

Folder Creation Trigger for Automations v2

Automations v2 can now start a run when a new folder is created, so adding a client folder can kick off an onboarding workflow or email the people who handle it. Choose Folder Creation as the trigger, pick the folder to watch, and set Folder Scope to direct child folders, folders exactly two levels below, or folders at any depth.

Each run receives the new folder's path and name, which a Send Email step can put in its subject and body; Send Email requires Custom SMTP. A new folder doesn't mean its uploads are finished. Copying a folder tree creates an item for every matching subfolder, so choose Direct child folders when only the top-level folder needs a notification.

HTML Bodies and Complete Emails for Inboxes and Automations v2

Inboxes and the Automations v2 Incoming Email trigger can now save an email's HTML body and the complete received email as an .eml file. HTML capture keeps the tables and formatting a plain-text body loses. Complete-email capture keeps the headers, body, and attachments together, so an existing process that reads .eml files can act on the sender and subject.

Both captures are off by default and work alongside the existing body capture, and attachments are still saved separately. On an Inbox, turn them on from the Inbound Email Settings tab or when you create the Inbox, as described in Choosing Which Email Content to Save. In Automations v2, select Save HTML Body or Save Complete Email in the trigger's Advanced settings, then store the files with a Copy File or Move File step, as described in What the Run Starts With.

Subfolder Summaries for Slack and Microsoft Teams

Slack and Microsoft Teams notifications can now post one summary per subfolder instead of one message per file. When a vendor uploads a hundred files into an Inbox submission folder, the channel gets a line such as Uploads/ACME: 10 uploaded, 2 deleted, and each submission's activity stays together.

Set Message delivery to Subfolder summary on a Slack or Teams notification. Each summary is sent after a quiet period you choose, from 15 to 300 seconds. A summary reports a burst of activity, so it doesn't confirm that a submission is complete. Existing notifications keep immediate delivery.

Slack and Teams Event Channel targets offer the same summaries for file activity events. A Site Administrator turns those events on from the Settings tab of Event Channels. Review your subscriptions first, because subscriptions with no event types selected begin matching file activity too.

Default Workspace Recipients in Custom Workspaces

Staff who keep their accounts in the Default Workspace can now receive Email Notifications for folders in a Custom Workspace, with no separate accounts created inside it. A Default Workspace user or group becomes an eligible recipient once a Site Administrator grants it a folder permission anywhere in that Workspace.

Workspace Administrators and Folder Admins can choose these recipients for the folders they administer while Share Users and Groups With Workspaces is on, which it is by default. Site Administrators find the setting on the Settings tab under Settings > Workspaces. Turn it off to keep these choices with Site Administrators; existing notifications stay in place.

In the notification form, select Choose specific users and groups not yet subscribed to this folder and pick them from the User or Group list. The All options cover only the Workspace's own users.

Child Site Activity Recorded on Both Sites

When a Parent Site works in a Child Site's folders through _/Sites/, those file actions now appear in both sites' History. The Parent Site records the _/Sites/<child-site-id>/... path, and the Child Site records its own path.

Each site's notifications, webhooks, and Automations respond to its own record, so existing ones on the Child Site now react to matching Parent Site operations. When a Parent Site uploads into a Child Site's intake folder, an Automation on either site can pick up the file. Activity performed directly within the Child Site is still recorded there only. Data and Automations Across Child Sites explains how to set up responses on each site.

Child Site IP Whitelist for Parent Site Users

A Child Site can now require Parent Site users, including Site Administrators, to connect from an address on its own IP whitelist. An organization can limit entry to a Child Site to a managed network, such as a virtual desktop with a fixed outbound address, while each person keeps a single Parent Site account.

Turn on Apply IP Whitelist to Parent Site Users under Security > IP Whitelist on the Child Site, or enforce it from the Parent Site through a Child Site Management Policy. The connection must satisfy both the Child Site's whitelist and the account's existing IP rules, as IP Whitelisting explains.

The setting controls entry to the Child Site, not access to its files. Parent Site Administrators can still work with Child Site files through the Parent Site's underscore folder and Parent Site Automations, as described in Accessing Child Sites.

Get The File Orchestration Platform Today

4,000+ organizations trust Files.com for mission-critical file operations. Start your free trial now and build your first flow in 60 seconds.

No credit card required • 7-day free trial • Live in minutes