Files.com signs people in with Auth0 over SAML or OIDC. So your file workflows use the login you already built your apps on. One account across Files.com and every other Auth0 app.
Auth0 is the login your apps already run on. Files.com connects to it over standard SAML or OIDC the way any other Auth0 app does, so file access uses the same login Auth0 manages. You manage identity in one place, and the rules for which folders each person reaches live in Files.com.
People sign in to Files.com with their Auth0 account. It is the same one they use for every other Auth0 app. There is no separate password to manage, so your team has nothing new to remember and you field fewer reset tickets.
Someone who logs in through Auth0 but has no Files.com account yet gets one created on the spot. Nothing to set up ahead of time, so you never provision a file account by hand and a new hire is productive the first time they sign in. The account simply exists the moment they first sign in. This is what JIT means.
The account is created on first sign-in. You never pay a seat for someone who is set up in Auth0 but never logs in to Files.com. You pay for people who use it, not names sitting in a directory.
Keep your second-factor check (MFA) in Auth0 for your own people. For outside accounts Auth0 does not manage, add Files.com’s own second factor (2FA). It covers SFTP, FTP, and WebDAV too, not just the browser. So no one slips past the second check by connecting over a protocol instead.
Files.com works with Auth0 over either standard. We recommend SAML because it handles more cases than OIDC, so you hit fewer edge cases setting it up and the sign-in works the first time.
Auth0 decides who gets to sign in. Files.com decides what each signed-in person can reach. That is 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 and every second-factor check is written to the Files.com audit log.
Grant access per person or per group, folder by folder, with the ability to block access and to fence in junior admins. The groups someone belongs to in Auth0 carry over to the folders and admin level they get in Files.com. So each person reaches only the folders their role allows, and you keep least-privilege without maintaining a second list.
Every sign-in, every second-factor check, and every permission change is written down. That is the record a SOC 2 review or a partner dispute asks for, kept for you without building anything.
For outside accounts Auth0 does not manage, Files.com can require its own second-factor check (2FA). It holds over SFTP, FTP, and WebDAV, not just the browser. So a partner can't skip the second check by switching to a protocol.
Files.com runs one of the most widely used SSO setups in managed file transfer, trusted by enterprise customers for sign-in-controlled file access. So you are not the first team putting your file workflows behind it.
People can start at the Files.com login page, which is the default. Or they can get launched straight into Files.com from an Auth0 dashboard. Both work, so sign-in fits how your team already moves between apps.
Auto-create on first login (JIT) makes accounts but never removes them. So an account a departed employee still has lingers until someone notices. Files.com fills that gap with rules that expire idle accounts, set end dates, and let you turn someone off by hand. A departing person actually loses access, so the account list stays right and your access review passes.
The groups someone belongs to in Auth0 come across at sign-in and become real Files.com folder permissions and admin levels. A new person lands in exactly the right folders the first time they log in.
The recommended way in. SAML handles the widest range of cases, so you hit fewer edge cases setting it up. People sign in to Files.com with their Auth0 account.
The other sign-in standard. People log in with their Auth0 account. A login-focused setup for teams already on OIDC.
Nothing extra to set up. Accounts are created the first time someone signs in. Good for getting started fast. Because it can't remove people, pair it with the Files.com controls that expire idle accounts, set end dates, and let you turn someone off by hand.
Someone clicks Sign in with Auth0 on the Files.com login page and logs in with the same Auth0 account behind your other apps. Files.com trusts that login and gives them their folders.
A newly set-up Auth0 user signs in to Files.com for the first time and their account is created automatically, with their groups carried over. Nothing has to be set up ahead of time.
Auth0 asks the person for a second factor (MFA) per your policy before letting them through. Files.com trusts that login and gives them their folders. It also requires its own second factor (2FA) on any outside accounts Auth0 does not manage.
Someone starts in an Auth0 portal and is launched straight into Files.com. Fully supported, alongside the usual start-from-the-login-page flow.
The folder permissions your Auth0 groups map into. Nine levels of access per folder.
Learn MoreEvery Auth0 sign-in and permission change is written to a record you can export.
Learn MoreFolder permissions and the second-factor check reach SFTP, FTP, and WebDAV, not just the browser someone signs into with Auth0.
Learn MoreRules that decide how long files stick around once an Auth0 user has put them in Files.com.
Learn MoreCommon questions about how Files.com connects to Auth0, what it costs, and what the integration actually does.
Start a free 7-day trial. Connect your Auth0 tenant to Files.com, sign in, and prove the integration works on your workload. No credit card required.
No credit card required • 7-day free trial • Setup in minutes