Folder Settings Within Remote Server Mount

Folder Settings let you apply file-processing rules and controls to files that remain on a Remote Server Mount. The settings belong to the Files.com site that configures the mount. Supported settings can be configured on the mount or its subfolders, and recursive settings from folders above the mount carry into it under their normal scope and inheritance rules.

Site Administrators and users with folder administration permission can view and configure supported settings within their administrative scope. The usual Folder Settings visibility rules apply, including limited configuration details for settings inherited from above a Folder Admin's scope.

Supported Settings and Inheritance

Supported settings include GPG encryption, decryption, and recryption; Auto Unzip; filename restrictions and renaming; Malware Scanning; Lock Subfolders; Permission Fences; Metadata Categories; Watermark Previews; Inboxes; Public Hosting; per-folder branding; and Webhook, Slack, Microsoft Teams, Amazon SNS, and Google Cloud Pub/Sub notifications. Recursive definitions above the mount apply unless a more specific definition replaces them according to the setting's nested effect. Malware Scanning retains its upload-only processing rule.

Settings that are never recursive, such as Organize Files into Subfolders and Automatically Create New User Folders Here When Users Are Created, act only at the folder where they are configured. The Folder Settings reference describes the individual settings.

For example, a recursive filename-extension restriction on Partners also governs uploads, copies, and moves to any folder within a mount at Partners/Intake. A retention rule on Partners has a different boundary: it does not delete files in that mount.

Retention and Storage Exceptions

File Expiration deletes files on the remote storage itself. A mount does not inherit this setting from a parent folder, so a parent retention rule cannot automatically delete the connected external files. To include those files in your retention policy, set File Expiration directly on the mount or on a folder within it.

Archive Removed Files applies only to native Files.com storage. It cannot be configured on a mount or on a folder within it, and a recursive rule above the mount does not apply inside it. Files deleted or overwritten through the mount are removed or replaced on the remote system without a copy in the mounting Site's archive path, so recovery depends on that system.

Storage Location (Region) also applies only to native Files.com storage. It cannot be configured on or within a mount, and an inherited region setting does not relocate the remote files. Their storage location is controlled by the remote system.

A Remote Server Mount cannot be nested inside another mount.

File Processing and Alternate Paths

GPG on Remote Server Mounts and Auto Unzip process files uploaded, copied, moved, or synced into the mount. Files.com stages the files in Native Storage for processing before remote delivery. Uploads use Buffered Uploads even when the Remote Server's setting is Never. Malware Scanning also requires buffered uploads, while retaining its upload-only scope. This also applies when the mount is reached through a Child Site or Connected Site folder at _/Sites/<site-id>, or through a Partner Channel Route Path. Configure processing where the destination files are stored; reaching the mount through another path does not skip its processing.

A mount of another Files.com site through a Files.com to Files.com Remote Server applies the mounting site's settings as for any other Remote Server Mount. Operations on the remote Files.com Site also follow that Site's own Folder Settings and Archive Only Mode. Each Site's administrator lock bypass relaxes only that Site's own locks. Its Archive Removed Files rule can preserve deleted or overwritten files in its own archive, while the mounting Site records the deletion at the mount path. Copies into the mount must meet both Sites' filename restrictions. This differs from Child Sites and Connected Sites, where the viewing site's file-processing settings do not carry into the other site's folders. Access Across Sites and Storage compares these arrangements.

Activity and Folder Lifecycle

Webhooks, Notifications, Automations, and Action/History Logging rely on the Files.com platform capturing information about operations performed. Files.com logs actions and history for file operations performed through Files.com itself. Activity performed on the remote system is captured when the mount's Remote Metadata Index is enabled, whose scheduled scans record files created and removed on the remote side as Remote-attributed actions. Automations, Webhooks, and Notifications triggered by file actions all fire on those actions.

Deleting a folder that has folder settings configured for it will also delete its folder settings. When a folder on a Remote Server Mount is deleted outside of Files.com, Files.com does not immediately remove its Folder Settings. Instead, the deletion is deferred for up to 72 hours to allow time for the folder to reappear, protecting existing configuration if the removal was temporary or accidental.