Adding a Remote Server

A Remote Server records the location, credentials, and connection settings Files.com uses to reach another system. Configure it before choosing a Mount for access to the remote working files or a Sync for a separate delivery. Adding the connection alone does not copy files or grant users access to them.

Site Administrators can add Remote Servers across the site. Workspace Administrators can add them within their Workspace. Users assigned an Integration-Centric Profile can add their own connections of the types their profile permits.

Connection Details

Select the native provider type when one is listed, or the protocol the remote operator supports. Use an internal name that identifies the relationship and environment, such as the partner and whether this is its test or production service. The provider reference supplies its required account, bucket, library, hostname, or endpoint details.

The connection's identity needs access to the intended location and operations. Listing a folder, writing a new file, replacing a file, and deleting one can require different permissions. For supported credentials, the Remote Server Credential Manager keeps shared secrets and their rotation in one place. OAuth connections instead require the provider's authorization for each Remote Server.

Connection Routing determines where connections originate. Coordinate the selected source addresses with the remote operator's firewall rules, or use Agent routing for an endpoint reachable from the Agent's network. The routing choice is separate from the remote storage location.

Connection Tests and Browsing

Use Browse to inspect the remote layout and intended path before creating a Mount or Sync. Browsing operates on the live remote files and can change or delete them when the credential permits it.

A successful test or listing establishes access for that operation, rather than every action a workflow will need. Test required reads, writes, and replacements with an agreed sample outside live processing. For cloud connections that use Direct Routing, the client also needs its own route to the provider; Files.com's successful connection test does not establish that reachability.

Concurrent Connections

FTP and SFTP expose a Max connections setting. Match it to the remote service's capacity and the operator's requirements. A higher value cannot override the remote service's own account or address limits. Consider the combined load from Mounts, Syncs, Automations, and other applications using the destination. Shared-address connections can also encounter popular-counterparty limits.

Buffered Uploads

Where available, Buffered Uploads determines whether Files.com receives a complete upload before forwarding it to the remote destination. This separates client receipt from remote delivery and uses temporary Files.com storage. Buffered Uploads explains defaults, delivery results, and processing that requires staging even when optional buffering is disabled.

Connections Back to the Same Site

A Remote Server connects to an external system or a different Files.com site. Files.com rejects a connection back to the same site using its own API key or its hostname and user credentials over FTP, SFTP, or WebDAV.

For work between folders on one site, perform the file operation or Automation directly against those paths. For separate Files.com sites, use the native connection when its access model fits the exchange.