Files.com to Files.com
Files.com can connect directly to another Files.com site as a Remote Server. Two organizations that each run Files.com, or one organization running multiple Files.com sites, can move files natively instead of falling back to FTPS, SFTP, or WebDAV between the two sites.
A company that receives files from a partner over SFTP can use this API-based connection when the partner also runs Files.com. An organization that splits into separately billed Files.com sites can use it for migration and ongoing transfers. The native connection supports parallel file-part transfers; actual performance depends on the workload and endpoints.
Once created, a Files.com Remote Server behaves like any other Remote Server. You can browse it, mount it as a folder with a Remote Server Mount, use it as a source or destination in a Sync, and copy, move, delete, download, and upload through it.
Parent and Child Sites
When one site is a Child Site of the other, or both are Child Sites of the same Parent Site, a Parent Site Administrator can use cross-site Automations and Syncs from the Parent Site without creating this Remote Server connection. Use the ordinary connector when separate sites need an explicitly credentialed connection.
Authentication
The connection authenticates to the other site with an API key generated on that site. Create a Remote Server with the Files.com type and enter the key.
The key must be a usable key from a different Files.com site. A key that is invalid, issued by the same site, expired, disabled, locked out, or deleted is rejected.
A same-site key is rejected because this integration is for crossing between Files.com sites. Within one site, perform the file operation directly against its source and destination paths rather than routing it through a Remote Server and back into the same site.
Access Permissions
The connection can only access what the API key itself is allowed to access, following the key's own permissions and any path restriction on it. A key that belongs to a single user, a Workspace, or a specific path exposes only what that user, Workspace, or path allows.
Ask your counterparty for a key that allows exactly what the connection needs, and grant the same way when you are the one issuing the key. A site-wide key hands the other site full access to everything on yours. A key restricted to one Workspace or path limits the exposure to the folders the connection actually uses.
Use a Files-Only key rather than a Full key for the connection. The connection only works with files and folders, which is everything a Files-Only key allows. A Full key also grants API access to users, permissions, and site settings that the connection never needs.
Set Up Both Sides
On the receiving site, create a dedicated account with access only to the folders the connecting site needs. For an external organization, use a Partner User when its scope fits; Partner permissions are shared across that Partner. Generate a Files-Only user API key and transfer it through a secure channel.
On the connecting site, create the Files.com Remote Server and enter the key. Give the connection a name that identifies the relationship and environment. Verify listing, reading, writing, and replacement behavior with representative files before enabling recurring transfers.
Maintain separate credentials for independently operated connections. To change access, update the remote account's permissions or the key's scope; to end the connection, revoke its key. A key from one site does not become a credential for that site's Parent or Child Sites.
Choose mounted access for work on the remote files themselves and a Sync for a replicated copy. Syncs & Automations covers selection, replacement permissions, and failure behavior.
Add Remote Server Mount
Remote Server Mounts are created by mounting them onto an empty folder in Files.com. We do not recommend mounting onto the Root of your site, although that is supported if you need it.
Add Sync
After creating the Remote Server, you can use it to perform Syncs between the other Files.com site and your own.
Automations
Folders configured with a Remote Server Mount to another Files.com site can be used with automations, so the other site can serve as a source location or destination for your automations.