The Celigo-hosted file server is a built-in SFTP server powered by Celigo Storage. It lets trading partners and other account-holders exchange files directly with you without any external infrastructure: you enable the server for an environment, create an isolated account for each account-holder with the permissions they need, and share the connection details. Account-holders connect with any standard SFTP client, using a password, an SSH key, or either. Files they upload are immediately available in Celigo Storage for your flows to process, and files your flows stage in the same folder are immediately available for pickup. This article explains what the file server is, how it differs from connecting out to someone else's server, how it relates to Celigo Storage, who can administer it, and how it's licensed.
Feature availability: The file server is included with the Professional and Enterprise editions and isn't available on the Standard edition (see Celigo platform editions). It doesn't require B2B Manager. The server is off by default — go to Resources , and then select File storage > SFTP file server to turn it on and work with it.
Hosted SFTP vs. external connections
Every other file capability in integrator.io assumes Celigo is the client: your flow reaches out to a server that someone else runs, using a connection you configure with their host and credentials (see Set up an FTP connection). 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 their permissions, 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 (see Set up a connection to Celigo APIs).
How the file server relates to Celigo Storage
The file server is a protocol front end for Celigo Storage. Each file server account is confined 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.
Accounts, permissions, and credentials
Each account-holder gets their own file server account with a username, a home folder, a set of permissions, and one or more credentials. Permissions — Read, Create, Modify, and Delete — control what the account-holder can do inside the home folder, so you can offer a write-only drop box or a read-only pickup folder rather than full access (see File server account permissions). Credentials can be a password, one or more SSH public keys, or both; registering multiple keys lets an account-holder rotate keys without downtime (see Manage SSH keys for a file server account). To create accounts, see Create and manage file server accounts.
Who can administer the file server
Server-level settings are limited to the account owner and administrators, while file server accounts can also be administered by users with Manage access to the integration whose system folder holds the account's home folder. For the full rules, see Who can administer file server accounts.
What is recorded
Configuration changes and account-holder activity are both recorded, in two different logs.
Configuration changes appear in the platform audit log, attributed to the user who made the change: turning the file server on or off, selecting the identifier, creating, editing, disabling, or deleting accounts, changing an account's permissions, setting or replacing a password, and adding or removing an SSH key. Audit entries never contain the password or key material.
Account-holder activity appears in the storage activity log: sign-ins, and every file operation, including downloads. Each entry shows the partner account name, the source IP address, and what the account-holder did.
A sign-in is recorded only when the file server can tell which account it was — every successful sign-in, and every failed sign-in to an account that exists, with the reason it failed. A username that doesn't exist, a key the account doesn't have, a connection stopped by a lockout or a rate limit, and an attempt made while the file server is turned off all leave no entry. Listings, searches, and operations refused by permissions are not recorded either. See Celigo Storage activity log.
Licensing and expiration
The file server is included with the Professional and Enterprise editions; there is no separate license or add-on to purchase (see Celigo platform editions). If your subscription lapses or moves to an edition that doesn't include the file server, account-holder connections stop, but your configuration — the server, its identifier, and all accounts with their permissions and keys — is retained and resumes working when your subscription is restored. Files already in Celigo Storage are unaffected.