Connect JumpCloud to Files.com and your team signs in with the login they already have. New people get access automatically. People who leave lose it automatically. JumpCloud stays the one place you manage who can do what. That includes the partners and outside accounts you exchange files with.
Lots of cloud-first IT teams use JumpCloud as their one directory for everyone in the company, often instead of an on-premises Active Directory. Connect Files.com to it and file access follows that same directory. JumpCloud handles who people are. Files.com decides which files each of them can reach.
Your team signs in to Files.com with their JumpCloud login, the same one they use everywhere else. There is no new password to hand out, so there is nothing for a person to forget, reset, or write on a sticky note. And there is no second list of users to keep in sync.
Add someone in JumpCloud and they get Files.com access right away, across the web, SFTP, and the Desktop App at once. Turn them off in JumpCloud and that access is gone. There is no script to run and nothing to remember on the day someone leaves, so a former employee can't keep reaching your files because the offboarding step got missed.
You can sync your whole JumpCloud directory into Files.com without paying for everyone in it. A seat only counts once a person signs in for the first time, so people who never log in cost nothing. You sync the full directory for clean provisioning and still pay only for the people actually using Files.com.
Keep your MFA rules in JumpCloud for the people who sign in through it. For outside accounts JumpCloud doesn’t manage, Files.com adds its own 2FA. That second factor also covers FTP, SFTP, and WebDAV, not only the website, so a partner pulling files over SFTP gets the same login check as a person in the browser.
A JumpCloud group decides which folders its members can reach and how much admin power they get. You manage who-can-do-what from the directory you already run, not in a second place. Move a person between groups in JumpCloud and their file permissions follow, so the access always matches their role with nothing to update by hand.
JumpCloud confirms who someone is. Files.com decides what they can reach. You get nine levels of access, per person or group, folder by folder, with the ability to block a folder and to fence off admins. And every sign-in, sync, and permission change is written to the audit log, so when a security review asks who could reach what and when, the answer is already recorded.
Turn a person off in JumpCloud and the next sync shuts off their Files.com account across the web, SFTP, and the Desktop App. This is what SCIM gives you that first-login account creation (JIT) can't: JIT makes accounts but never removes them. So your access list never drifts, and the offboarding can't be forgotten because no one has to do it by hand.
Every create, update, and removal JumpCloud sends is written to a detailed SCIM Log in plain JSON. If a new account didn't show up the way you expected, you can see exactly what JumpCloud sent and why, so you fix the problem from the record instead of guessing.
Set access per person or per group, folder by folder. You get nine levels, the ability to block a folder, and fenced-off admins. JumpCloud says who someone is. Files.com decides what they can reach, so each person sees only the folders their job needs and an admin can’t wander into data they shouldn’t.
For outside accounts JumpCloud doesn't manage, you can require Files.com 2FA. That requirement holds over FTP, SFTP, and WebDAV, not just the browser, so there is no protocol left open as the weak way in when a review asks whether every door needs a second factor.
Files.com runs one of the most widely used SSO setups in managed file transfer, relied on by a large base of enterprise customers to keep file access tied to their directory. So you are not the one shaking out a brand-new integration. This path is already running in production at companies with the same governance demands you have.
With SCIM 2.0, JumpCloud creates, updates, and turns off Files.com users on its own. JumpCloud stays the one place you change who has file access, so you never edit two systems and the two can't fall out of sync.
If you don't turn on SCIM, Files.com makes an account the first time someone signs in (this is called JIT). It's simple to start with, and it can't remove people later. Turn on SCIM when you need departing users shut off automatically, so you get the easy start now and the clean offboarding when governance asks for it.
This is the main connection. Set Files.com up as an app in JumpCloud over SAML, then point Files.com back at JumpCloud. Now your team signs in with their JumpCloud login, so there is one less password for you to manage and one less account for an attacker to phish.
Turn on SCIM to have JumpCloud create, update, and remove Files.com users by itself, and to keep group memberships in sync. This is what shuts off access automatically when someone leaves.
Nothing extra to set up. This is what runs when SCIM is off. An account is made the first time a person signs in, so you can be live the same day with no provisioning to configure. It can't remove people, so add SCIM when you need that.
A person clicks Sign in with JumpCloud on the Files.com login page, confirms their identity through JumpCloud, and lands in their account. No separate password.
When you assign someone to Files.com in JumpCloud, SCIM creates their account, drops them in the right groups, and applies their folder permissions. All of this happens before they ever sign in, so a new hire has exactly the right access on day one and you never touch Files.com to set them up.
Turn someone off in JumpCloud and the next sync shuts off their Files.com account across the web, SFTP, and the Desktop App.
When it's time to refresh the SCIM token, Files.com creates a new one and emails you a reminder. Paste it into JumpCloud before the old one expires, so provisioning keeps running with no gap and you don't get surprised by a token that quietly stopped working.
The folder-by-folder permissions, with nine levels, that your JumpCloud groups feed into.
Learn MoreWhere every JumpCloud sign-in and provisioning event is recorded in a record you can export.
Learn MoreHow 2FA and folder permissions reach FTP, SFTP, and WebDAV, not just the browser a person signs into.
Learn MoreRules that decide how long files stick around once someone has put them in Files.com.
Learn MoreHow Files.com connects to JumpCloud, how seats are counted, and what the integration actually does.
Start a free 7-day trial. Connect JumpCloud over SAML, turn on SCIM, and watch your team sign in with the login they already have. No credit card required.
No credit card required • 7-day free trial • Setup in minutes