The Celigo-hosted file server is a built-in SFTP server powered by Celigo Storage, allowing account-holders to exchange files directly with you without requiring external infrastructure. Simply enable the server for your environment, create an isolated account for each account-holder, and share their login credentials. Account-holders can connect using any standard SFTP client; uploaded files immediately save as standard Celigo Storage files for your flows to process, while staged files in the same folder are instantly available for account-holder pickup.
This article explains what the file server is, how it differs from connecting out to an account-holder's server, how it relates to Celigo Storage, and how it is licensed. To set one up, see Enable a file server for an environment.
Feature availability:
- The file server is an add-on, licensed independently of B2B Manager, and is off by default. Contact your account manager to add it to your subscription. Once added, go to Resources
> File storage, then select File server from the top of the page to work with the server.
- Only account owners and administrators can enable a file server or administer file server accounts.
Hosted SFTP vs. external connections
Every other file capability in integrator.io assumes Celigo is the client: your flow reaches out to a file server that someone else runs, using a connection you configure with their host and credentials (see Set up an FTP connection, Export files from an FTP server, and Import or transfer files to an FTP server). The Celigo-hosted file server inverts that relationship — Celigo runs the server, and your account-holder is the client.
This changes who does the work. Your account-holder needs no Celigo account, no flow, and no integration knowledge; they connect with the SFTP client they already use (such as OpenSSH, WinSCP, or FileZilla) and see only their own home folder. You configure everything on your side: the server, the accounts, and the flows that consume or stage the files.
Note
Don't create an FTP connection in integrator.io that points at your own file server. Connection validation fails with an error directing you to the Celigo APIs connector, which is the supported way for flows to read and write Celigo Storage files.
How the file server relates to Celigo Storage
The file server is a protocol front end for Celigo Storage. Each file server account is chrooted to a home folder in Celigo Storage, and everything inside that folder is ordinary storage content:
- A file an account-holder uploads over SFTP appears immediately on the File storage page, is metered against your storage allowance, and can be consumed by flows and the API like any other storage file.
- A file a flow stages into the home folder is available for the account-holder to download.
- Deletes are soft — items an account-holder deletes go to the recycle bin and count toward your allowance until purged, the same as deletes made in the UI (see Work with files and folders in integrator.io).
- SFTP uploads follow your account's storage overage behavior.
Note
Some SFTP clients overwrite files by uploading a temporary file, deleting the original, and renaming. Because deletes are soft, each overwrite in that pattern leaves a soft-deleted copy in your recycle bin that counts toward your allowance until it is purged. At high transfer volumes this can consume the allowance quickly.
What is recorded
Configuration changes are audited; account-holder activity is not. Enabling or disabling the file server, selecting the identifier, and creating, editing, disabling, or deleting accounts — including setting or replacing a password — all appear in the platform audit log, attributed to the user who made the change.
Account-holder file operations and authentication attempts are not recorded. You cannot see that an account-holder connected, failed to sign in, uploaded, overwrote, or deleted a file. If you need to confirm that an account-holder sent a file, check the folder contents on the File storage page.
File server limits and supported operations
Understand features, limits, and protocol behavior for the Celigo-hosted SFTP file server to configure integrations or assess client compatibility. Key details include the following:
- Supported operations - Full folder permissions (list, upload, download, move, rename, delete) via SFTP only; no shell access, SCP, or port forwarding.
- Storage behavior - Backed by Celigo Storage (object storage), so directory deletes are recursive, deleted items move to the recycle bin, and non-zero offset/append writes are unsupported (interrupted transfers must be re-sent whole).
- Limits & rules - Uploads overwrite existing files with stable file IDs, and full-path name rules (1,024-byte limit) follow standard Celigo Storage policies.
Licensing and expiration
The file server is licensed as an independent add-on. If the license expires, account-holder connections stop, but your configuration — the server, its identifier, and all accounts — is retained and resumes working when the license is renewed. Files already in Celigo Storage are unaffected by license expiration.