Setting Up a Remote Server Mount
A Mount attaches one remote location to one Files.com folder. Configure the Remote Server connection first, then use its Browse action to identify the remote location and confirm access. The mount exposes those working files; it does not import them into Files.com Native Storage.
Site Administrators and Workspace Administrators configure Mounts within their administrative scope. A Workspace Administrator's local mount folder must be within that Workspace.
Local and Remote Locations
The mount combines a connection with two paths. The local path is where Files.com users and workflows reach the files; the remote path is where those operations take effect.
| Setting | Meaning |
|---|---|
| Remote server | The connection supplying remote access. |
| Remote Folder | The location on that system to expose through the mount. Select a folder the connection can access. |
| Local Folder | An empty Files.com folder that becomes the mount point. |
| Name and Description | Optional labels that help your team identify the mount and its purpose. |
An empty subfolder is the recommended mount point for most deployments. Mounting the site root is supported, but makes the remote system the storage behind the entire site. For that arrangement, consider a Child Site with its root mount configured through the CLI or API.
A Sync using the local mounted path transfers to or from the remote storage behind it. Files.com users need folder permissions on that path, while the remote credential independently needs the rights required for each operation.
Remote Folder Scope
Files.com keeps the paths requested through a mount within the selected Remote Folder. The remote server determines which files those paths reach: its symbolic links or WebDAV redirects can lead outside that folder.
For example, a link at /exports/finance/archive on an SFTP server can point to /exports/hr. Mounting /exports/finance makes the HR files reachable through archive if the remote account has access. Files.com users can then act on those target files according to their folder permissions and the remote account's rights. To exclude them, restrict the remote account's access on that server; choosing the mount path alone does not restrict the link's target.
Mount Setup Restrictions
The local mount folder must contain no files or subfolders. Mounting changes which storage serves that path and displays the remote folder's contents; it does not merge them with existing native content. Use the migration guidance when existing files need to move to remote storage.
For a Partner Channel, mount on a separate folder and use it as the Channel's Route Path. A mount cannot be added on or above a Channel's base folder, To Partner or From Partner folder, or Managed Folder. These folders remain native so the Channel can enforce its structure and routing rules.
Storage Location (Region) applies to native storage. It cannot be configured on or within a mount, and an inherited region setting does not relocate remote files. Their location remains under the remote system's control. A mount also cannot be nested inside another mount; supported Folder Settings have their own inheritance and processing rules.