Content Collaboration
Connect the document services your staff and partners already work in to the file exchange your organization runs through Files.com. A partner can continue delivering documents in Box, or an internal team can keep its working library in SharePoint, while Files.com provides access through its own accounts, protocols, sharing, and automated workflows.
The connection reaches the files its remote account or application can access. A Remote Server Mount exposes that location through a Files.com folder, so changes act on the remote documents. A Sync delivers a separate copy for another application, recurring collection, or migration. Choose which system should hold the working copy before choosing the transfer arrangement.
Account Ownership and Access
An administrator-managed connection fits an organizational library or a partner feed maintained by your team. Use an identity your organization can maintain when staff change. A person's own account is a different arrangement: Integration-Centric Profiles let users authorize and maintain their individual connections without an administrator collecting their credentials.
Native connectors use the provider's HTTPS API. Egnyte and ShareFile instead use their supported file transfer protocols. In either arrangement, the provider's permissions limit the connection, while Files.com folder permissions independently control access through a mount. Signing in to Files.com does not pass each user's identity through to the document service.
Delivery and Ongoing Operation
Collaboration services can limit request rates, file names, and the operations an account may perform. Connecting them does not remove those limits. Buffered Uploads lets Files.com receive uploads before delivering them at the rate the provider accepts. With buffering, a completed client upload confirms receipt by Files.com; dependent work must use the onward delivery result.
Changes made directly in the document service also affect mounted files. A mount's Remote Metadata Index discovers remote-side arrivals and removals on scheduled scans when a workflow needs those changes recorded in Files.com. A mount alone does not create an independent backup or notify Files.com immediately about every remote change.
OAuth connections refresh their access tokens automatically while the provider's authorization remains valid. Revoked access, account changes, or provider policies can require re-authentication. Keep an owner for that authorization as well as for the workflow using it.