Box

Files.com connects to Box in two ways: Remote Server Mount and Sync.

A Remote Server Mount connects a specific folder on Files.com to Box in real time. That folder becomes a client, or window, into the files stored in Box.

Once you configure a Mount, any operation you perform on or inside that folder acts directly on the remote in real time. Dropping a file into that folder, deleting a file, creating a subfolder, or performing any other file or folder operation your Files.com user has permission for passes through to the remote in real time.

This enables use cases such as accessing files on a counterparty (client or vendor)'s cloud without provisioning individual access to individual users, reducing storage costs by using on-premise or bulk storage, and enabling applications to access third-party clouds via Files.com API, FTP, SFTP, or Files.com Apps.

Files.com's Sync feature pushes or pulls files to or from remote servers. The files exist in both places at the end of the sync process.

A sync can be a "push," where files from your Files.com site are transferred to the remote server, or a "pull," where files are transferred from the remote server to your Files.com site.

Add Box as a Remote Server

Create a new Remote Server for your site, and select Box as the remote server type.

You must provide an Internal name for this connection. If you're managing multiple remote servers, make the name clear enough to easily identify this particular connection.

The options for specifying Dedicated IPs and Data Regional Routing will only appear if your site is configured to allow those options. Dedicated IPs are only available when a Custom Domain has been configured. Data Regional Routing is only available if your top-level, or root, folder is set to a non-USA geographic region.

Once your new Remote Server is saved, complete the authentication and authorization with Box. A popup displays the Box login form. Logging in connects your Files.com site with your Box account.

After your Remote Server is connected, you can use it with Files.com as either a Remote Server Mount or Sync.

Box Authentication and Authorization

Make sure the permissions of the Box user account are correct. Files.com can only perform actions allowed for the Box user. Authenticate using a Box user account that has "Editor" permissions or higher.

Download, preview, and edit actions for watermarked files are not allowed for Box user accounts with "Viewer" permissions unless the user performs those actions on the Box platform itself. "Viewer" actions that succeed on the Box platform do not succeed for the same user when they access Box from another platform, such as Files.com.

Using Multiple Box Accounts

You can create as many Box Remote Servers as required. Repeat the above instructions and enter different credentials each time the Box login page is presented.

If you are using Single Sign-On (SSO) with Box, your web browser always tries to log you in using your currently logged-in credentials. The popup Box login page automatically logs you in without giving you the option to enter different credentials. This is normal web SSO behavior. To work around it, log out of Box within your web browser before connecting the new Remote Server, use an incognito web browser window, or use a different computer and web browser that hasn't logged into Box yet.

Add Remote Server Mount

Remote Server Mounts are created by mounting them onto an empty folder in Files.com. We recommend that this folder not be the Root of your site, although the Root is supported if you need it.

Add Sync

After creating the Remote Server, you can use it to perform Syncs between your remote server and Files.com.

Automations

Folders configured with a Remote Server Mount to Box can be used with automations as source locations or destinations.

Folder Size Recommendations for Box

Box has lower performance characteristics than many other storage platforms, particularly for folders containing large numbers of items. Folder size has a direct impact on reliability, sync performance, listing speed, and API responsiveness. Our analysis shows that Box's performance begins to decline at lower folder sizes than most other remote providers.

Box performs best when folders remain relatively small. Folders containing 250 to 500 items offer the most stable experience. Within this range, folder listings, sync operations, and API-driven workflows run consistently.

Folders that grow to around 1,000 items still function acceptably, but listings become noticeably slower and sync cycles run longer. This size represents the upper end of what is practical when integrating with Box.

Once a folder exceeds 1,000 items, performance degradation becomes likely. Browsing and syncing experience delays or intermittent timeouts. We recommend maintaining folders well below this threshold.

Case Sensitivity

Be aware of case sensitivity differences when copying, moving, or syncing files and folders between Box and other storage locations. Box is a case insensitive system whereas other systems may be case sensitive. This can cause files to be overwritten and folders to have their contents merged when their case-insensitive names match.

What To Do When Your Remote Server Connection Is Disabled

Because Box uses the OAuth authorization protocol, authentication errors can occur even after your remote server is configured and running smoothly for some time. When one of those errors happens, Files.com disables your Box remote server connection and records the error in your External Events log.

When you've resolved the problem that caused the authentication error, re-enable your remote server by saving its configuration. Even if you don't make any changes to the configuration, saving the record causes Files.com to re-enable the connection, and any associated mounts and syncs begin working again.

Troubleshooting

Cannot Download File

When you attempt to download a file from a Box Remote Mount folder, the errors Box errored while trying to Download: '403:' and Could not download {path} due to: indicate that the Box user only has "Viewer" permission and is attempting to download a watermarked file.

Box only allows watermarked files to be downloaded directly from its own platform via the online viewer app. Watermarked files cannot be downloaded any other way by "Viewer" permission users of Box.

Change the Box user's permission to "Editor" to resolve this issue.