March 2024

March 2024 added Email Verification as a new two-factor authentication method, plus a series of admin, GPG, and developer-tooling refinements.

The list of features highlights the most notable updates, including key improvements and new capabilities. It also includes changes that may require action, such as updates affecting security, compliance, or system configurations. Reviewing these updates ensures you stay informed and can take any necessary steps to maintain smooth operations.

New 2FA Method Available

Files.com now supports Email Verification as a two-factor authentication method. This new method is disabled for your site by default, so an administrator must enable the method for your site before it can be assigned to any user.

Learn more about 2FA methods.

Minor Updates

SMS for 2FA Support for NZ and FI

We've added New Zealand and Finland to the list of countries compatible with SMS 2FA messages. If there are other countries you'd like us to support for SMS two-factor messages, please let us know.

Learn more about 2FA.

Desktop App Updated

New updates to the desktop app address issues relinking a file while using InDesign. For the best experience working with InDesign, upgrade to the most recent version of the Files.com Desktop app.

Learn more about the Desktop app.

CLI App Support For Automation Custom Schedules

The Command Line Interface (CLI) Application has been updated with new flags for creating Automations. You can now specify a custom schedule when creating an Automation using CLI. Update to the most recent version of the CLI to take advantage of this feature.

Learn more about CLI.

Export Login History Button

The Users page includes a button to export a listing of all user logins within a date range. The button used to sit at the bottom of the page; we've given it its own tab on the Users page to make it more visible.

GPG On-Demand Key Generation

When configuring auto-encryption or auto-decryption for a folder, the web interface lets you create a new key and store it in the GPG Key Manager without interrupting your workflow. This reduces the friction of configuring encryption settings for your site. No action is required to take advantage of this feature.

Learn more about automatically encrypting or decrypting files.

Improved Display of SSH Keys

By popular demand, the web interface can now include the SHA256 Fingerprint in the list of SSH Keys. You can toggle the visibility of this column whenever you like.

Learn more about configuring SFTP/SSH Keys.

New WebDAV Settings Page

We've added a new page to the web interface for your WebDAV-related settings. We recommend the Desktop app over WebDAV whenever possible, but settings and information belong where you already look for them. No action is needed to enable this update, and no settings were changed.

Learn more about using WebDAV for your site, or about using our Desktop app instead.

Improved Usage Dashboard

We've updated the Usage dashboard in the web interface to make it clear that the user counts displayed represent Billable Users. There's nothing you need to do to enable this update.

Learn more about how Usage is calculated.

User Page Reflects Disabled Protocols

While editing a user in the web interface, the form for a user's allowed protocols no longer lets you grant a user access to a protocol (FTP, SFTP, WebDAV) that has been disabled for your site. Granting access to a disabled protocol never actually allowed that user to connect, so the form now reflects the site-wide limitation that is enforced.

Learn more about enabling and disabling FTP, SFTP, or WebDAV for your site.

Developer Documentation Updates

We've clarified that the restapi_permission for users grants access through the API, the web interface, and the desktop application. The property name has caused confusion in the past, and we're always working to improve the developer experience.

See our developer documentation.

SDK READMEs Updated Regarding End-Of-Life Frameworks

We work to keep our SDKs up-to-date, secure and ready-to-use. Because of that, we do not support frameworks or dependencies that have reached end-of-life status. Our READMEs have been updated to better reflect which versions of frameworks are supported.

Check out our SDKs on Github.