Software Updates

Files.com delivers its File Orchestration Platform as software as a service (SaaS). We operate and update the cloud service, so your site receives new capabilities, improvements, and fixes as we release them. Continuous delivery lets us improve file exchange for people and business systems without each customer ever having to run an upgrade project.

Continuous Releases

We ship updates regularly, usually several times per day during the work week. This pace lets us put useful improvements into customers' hands promptly and keep improving the service they already use.

We try to avoid changes that create challenges for customers. When we move something in the web interface, we keep navigation intuitive and support it with search, so you can find features and settings without relying on their previous location. Changes generally fit smoothly into everyday use. Occasionally, a change may call for a small adjustment to a procedure or training material.

We deliver updates across our customer base, so individual customer approval is not part of our standard release process. We also cannot notify every customer in advance of every change. When preparing procedures and training, keep the possibility of interface changes in mind.

New Capabilities and Security Controls

New capabilities are typically available automatically to eligible customers as soon as we release them, without requiring each customer to opt in. Some include an opt-out so your organization can choose whether to use them. Other capabilities need configuration before they perform work. The feature's documentation explains its defaults, plan requirements, and controls.

For example, Site Administrators can turn off AI features when their organization does not permit their use.

We apply new security protections automatically where we can safely do so. When we cannot safely enable a new control automatically, we leave it for administrators to configure and describe it in What's New. Those announcements help you adopt protections that require a decision about your organization's environment or workflows.

Client Software and Security Updates

Files.com updates the cloud service on your behalf. Software your organization installs or includes in an integration has its own update process. We regularly ship updates to the Agent, Desktop App, Mobile App, SDKs, and separately distributed connectors, including security updates. We do not separately announce the security content of each release. Install all updates and keep this software on the latest version to receive those corrections, rather than waiting for a security-specific announcement.

The Files.com Agent has a built-in update process that keeps service installations current automatically by default. You can turn automatic updates off when your organization manages deployment itself, but your team must then make sure it installs updates. An Agent that is still transferring files successfully can still need an update to receive a security correction.

The Desktop App also keeps itself current through automatic updates. If your IT team disables those updates for centralized deployment, it takes responsibility for installing new versions across your organization. Keep the Mobile App current through your device's app updates as well.

The same recommendation applies to Files.com SDKs and our connectors for Boomi and MuleSoft: use the latest version. If you pin an SDK dependency or select a connector version for your integration, include updates in your deployment process. Updating the cloud service does not update those components for you.

Your Organization's Change Controls

Read What's New regularly. We publish it once a month, usually toward the beginning of the month, to describe new capabilities and the controls available for them. Review those capabilities against your organization's requirements and use the documented controls to disable or restrict a feature when needed. An opt-out for one feature controls that feature; it does not change the site's overall release model.

Enterprise Support customers whose formal requirements call for reviewing interface updates before introducing them to staff can purchase the GxP Validation Option for the Web Interface. It gives change-control teams time to review changes and publish any corresponding updates to internal documentation, procedures, and training. We charge substantial additional costs for this option, and it delays improvements and fixes to the interface. We recommend the standard release process for most customers. This option is intended for the small number of organizations whose formal requirements justify the additional control and work.