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.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
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 signs in through Auth0 with no Files.com account gets one created on the spot. That is JIT provisioning: you never set up a file account by hand, and a new hire is productive the first time they sign in.
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.
Auth0 decides who gets to sign in. Files.com decides what each signed-in person can reach, and keeps the record proving it.
Grant access per person or per group, folder by folder, with the ability to block access outright and to fence in junior admins. Each person reaches only the folders their role allows.
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.
Export a complete report of who can reach every folder as a CSV. When an access review or a security questionnaire lands, the answer is one export instead of a hand-built spreadsheet.
Files.com runs file operations for banks and healthcare companies in production. You are not the first team putting file workflows behind your identity provider.
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 a departed employee’s account 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 first sign-in and become real Files.com folder permissions and admin levels. You can also set default groups that every new Auth0 user joins. Either way, a new person lands in the right folders the first time they log in.
The recommended way in. SAML handles the widest range of setups, so the sign-in works the first time. Keep at least one admin on password sign-in, and an Auth0 outage can never lock you out of your own site.
The other sign-in standard. If your Auth0 apps already use OIDC, Files.com connects that way too, with the same sign-in for your team.
Nothing extra to set up. Accounts are created the first time someone signs in. Good for getting started fast. JIT creates accounts, never removes them, so pair it with the Files.com controls that cut off departing people.
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 new Auth0 user signs in to Files.com for the first time and their account is created automatically, with their Auth0 groups carried over. Nothing has to be provisioned ahead of time.
Auth0 asks the person for a second factor per your MFA policy before they ever reach Files.com. Your existing login rules cover file access without a separate policy to maintain.
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 hold over SFTP, FTP, and WebDAV, the same as in 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 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.”
How Auth0 sign-in works on Files.com, from a person’s first login to the day you shut off their access.
Yes. Files.com works with Auth0 over either SAML or OpenID Connect (OIDC). We recommend SAML because it handles a broader range of cases than OIDC.
Files.com creates a person's account the first time they sign in through Auth0 (this is called JIT provisioning). JIT can create accounts, but it cannot remove or disable them.
No. Files.com provisions Auth0 users on first sign-in (JIT), not through the automatic-sync system (SCIM), so it does not turn off departing people on its own. To cut off departing people, use the Files.com controls that expire idle accounts, set end dates, and let you disable someone by hand.
No. Files.com bills for people who use it, not for names in a directory. The Auth0 account is created only at first sign-in, so you never pay a seat for someone who is set up in Auth0 but never logs in. See how Files.com pricing counts seats.
Yes. With Auth0 you can start at the Files.com login page (the default) or get launched into Files.com straight from an Auth0 dashboard. Both are supported.
No. Signing in with Auth0 covers the browser and the Files.com Desktop App. For SFTP, FTP, or WebDAV, an Auth0 user adds an SFTP key or an API key to their Files.com account and connects with that.
Yes. Set your second-factor check (MFA) in Auth0, where it runs before anyone reaches Files.com. For outside accounts Auth0 does not manage, Files.com can also require its own second factor (2FA), which covers SFTP, FTP, and WebDAV.
Removing someone in Auth0 stops their Auth0 sign-in to Files.com right away, but it does not disable their Files.com account. Any SFTP key or API key on that account keeps working until the account is turned off. Files.com closes that gap with lifecycle rules that expire idle accounts, end dates you set in advance, and the ability to disable someone by hand.
Yes. Internal users sign in through Auth0 while partners use Files.com credentials scoped to their own folders. Every sign-in from both lands in the same audit log.
Start a 7-day free 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 • Live in minutes