Does your login system speak SAML 2.0? Then it can sign your team in to Files.com, the File Orchestration Platform, and keep accounts synced with SCIM. That covers Ping Identity, Cloudflare SSO, IBM Security Verify, Rippling, Google Workspace SSO, and anything else. You don't need a named integration for your provider.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
SAML is the open standard that lets your login system tell an app who someone is. Your people log in to Files.com with the account they already have, and accounts are created and removed straight from your directory. So the directory you already run stays the one source of who gets in, and there's no second login to manage on the side.
Ping Identity, Cloudflare SSO, IBM Security Verify, Rippling, Google Workspace SSO, and any other SAML 2.0 provider all sign people in through one general-purpose SAML setup. So you don't wait for a named integration to ship, and you don't get stuck if your provider is one Files.com never builds one for.
Turn on account sync (SCIM) and access follows your directory. Someone gets Files.com access the moment they appear in it, and loses it on the next sync after you turn them off. So you never grant or revoke file access by hand.
A seat starts counting only once that person signs in for the first time. So you can sync your whole directory into Files.com and not pay for the people who never log in, and your bill tracks real usage instead of headcount.
Keep your second-factor check (MFA) in your own login system. For accounts it does not manage, add Files.com’s own second factor (2FA). It covers SFTP, FTP, and WebDAV too, not just the browser. So a stolen password alone never opens your files, on any way in.
SAML lets you set up the same provider more than once on a single site, one setup per team or business unit. OAuth-based providers are limited to one each.
Your login system decides who is allowed in. Files.com decides what each person can reach once they are in. That means nine levels of access, set per person or per group, folder by folder, with the ability to block access and to fence in junior admins. Every sign-in, account sync, and permission change is written to the Files.com audit log.
If your login system supports it, Files.com creates accounts, keeps them current, and turns them off automatically. This is SCIM. You get the same automatic sync the named integrations get. So onboarding and offboarding happen in your directory and nowhere else, with no second list to keep up by hand.
Files.com keeps a separate, detailed log of every account it creates, changes, or turns off. When a sync does not land the way you expect, you can see exactly what your login system sent. So you fix the problem at the source in minutes instead of guessing, and you have a record to show the auditor.
Map your SAML groups straight to folders and admin levels. Nine levels of access, set per person or per group, keep access defined where your security team already manages it. So who can reach what stays in step with your directory, and least-privilege holds without a second list to maintain.
Export a complete report of every user's folder access as a CSV. The access review becomes a download, not a week of screenshots.
The way in for any SAML 2.0 provider that doesn't have its own named integration. In Files.com you pick SAML (Other Provider) and point it at your provider with a Metadata URL, an XML file, or a certificate fingerprint. People then sign in with their existing account, so there's no new password to issue and nothing extra for them to remember.
Turn this on when your login system supports it, for automatic create, update, remove, and group sync. It runs over the SAML setup, so accounts and groups stay in step with your directory and there's nothing to keep current by hand.
Pick JIT as the provisioning method, and Files.com creates each account the first time that person signs in. It's the lightest way to start before you need full automation.
A company running Ping Identity, Cloudflare SSO, IBM Security Verify, or Rippling sets up the general-purpose SAML connection. People then sign in to Files.com with the account they already use for everything else.
A login system that supports account sync (SCIM) creates Files.com accounts on its own, with the right groups and folders applied the moment each account is made. So a new hire can reach exactly the right files on day one, with no setup ticket waiting in your queue.
Turn off someone in your SAML login system. With account sync (SCIM) on, the next sync turns off their Files.com account too. Web, SFTP, and Desktop App, all at once. So the person you offboarded loses every way in, and you never chase a leftover account a week later.
Set up the same provider twice, one per business unit. Each gets its own name on the Files.com login page. Each unit's access stays separate, so one site can serve several teams without their files or sign-ins crossing over.
The folder permissions your SAML groups map into. Nine levels of access per folder, with the ability to block access and to fence in junior admins.
Learn MoreEvery SAML sign-in and account sync is written to a tamper-proof record you can export, so the answer to who reached what is already there when the auditor asks.
Learn MoreThe folder permissions a SAML user gets in the browser hold over SFTP, FTP, and WebDAV too.
Learn MoreRules that decide how long files stick around once a SAML user has put them in Files.com.
Learn More“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What to know before you connect your SAML 2.0 login system to Files.com, from account sync to what you pay.
Files.com has a general-purpose SAML setup that works with any SAML 2.0 provider, including Ping Identity, Cloudflare SSO, IBM Security Verify, and Rippling SSO. If your login system speaks SAML 2.0, it connects to Files.com.
Yes. Files.com syncs accounts automatically (SCIM) over any of its SAML setups, including the general-purpose one, whenever your login system supports SCIM. This runs over SAML, not OAuth or OIDC.
No. You can sync your whole directory into Files.com and not pay for the people who never log in. A seat starts counting only once that person signs in for the first time, so what you pay tracks real usage, not directory size.
Yes. Over SAML, you can set up the same provider more than once on a single Files.com site, for example a separate setup per business unit. OAuth-based providers are limited to one each.
Yes. Files.com keeps a separate, detailed log of every account it creates, changes, or turns off, so a sync problem is easy to track down. You can see exactly what your login system sent.
Yes. People can start at the Files.com login page (the default) or get launched into Files.com straight from your provider's dashboard.
Yes. A person has to already exist in Files.com for general-purpose SAML login to work, unless you have turned on auto-create on first login (JIT) or automatic account sync (SCIM) to make accounts for you.
No. Signing in with SAML works for the browser and the Files.com Desktop App. SFTP, FTP, and WebDAV connections authenticate with an SSH key or an API key instead.
Start a 7-day free trial. Connect your SAML 2.0 login system, run a test sign-in, and watch accounts sync from your own directory.
No credit card required • 7-day free trial • Live in minutes