One Login Across Every App
People sign in to Files.com with their OneLogin account — the same one they use for every other OneLogin app, with no separate password for file access.
Files.com signs people in with OneLogin over SAML and syncs accounts over SCIM, so partner SFTP, controlled outside file exchange, and scheduled drops all sit behind the same login your people already use. Accounts created or removed in OneLogin update in Files.com on their own.
OneLogin handles sign-in, the second-factor check, and the whole hire-to-leave lifecycle across your apps. Files.com signs in through it over SAML and syncs accounts over SCIM, so moving files comes under the same login and the same controls — accounts created and turned off in OneLogin update in Files.com on their own.
People sign in to Files.com with their OneLogin account — the same one they use for every other OneLogin app, with no separate password for file access.
The moment someone is added in OneLogin, they get their Files.com access. The moment they are turned off, they lose it — across the web, SFTP, and the Desktop App at once. A new hire is set up right on day one and gone the day they leave. This is what SCIM does.
You can sync your whole OneLogin 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.
Keep your second-factor check (MFA) in OneLogin for your own people. For outside accounts OneLogin does not manage, add Files.com’s own second factor (2FA) — and it covers SFTP, FTP, and WebDAV too, not just the browser.
A OneLogin group maps straight to the folders that group can open, or to an admin role — so access stays defined in OneLogin, where your security team already runs it.
OneLogin decides who gets in. Files.com decides what they reach once they are — 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.
Turn off a departing employee in OneLogin and the next sync turns off their Files.com account too — web, SFTP, and Desktop App, all gone. No access left lying around.
Files.com keeps a separate, detailed log of every account it creates, changes, or turns off from OneLogin, so if a sync does not land the way you expected, you can see exactly what OneLogin sent. It sits alongside the main audit log.
Grant access per person or per group, folder by folder, with the ability to block access and to fence in junior admins. Which OneLogin group someone is in decides their folders and admin level.
Outside partner accounts created in Files.com can be required to use Files.com's second-factor check (2FA) — and it holds over SFTP, FTP, and WebDAV, not just the browser.
Files.com runs one of the most widely used SSO setups in managed file transfer, trusted by a large base of enterprise customers for sign-in-controlled file access.
Create people and groups, keep them current, and turn them off — all driven from OneLogin. Change the directory and Files.com follows, with no one touching the file platform (this is SCIM).
If you have not turned on account sync (SCIM) yet, Files.com just creates the account the first time someone signs in (this is JIT). It cannot remove or disable people, though — so use SCIM when you need leavers cut off automatically.
Connect more than one OneLogin instance or app to a single Files.com site, so separate business units can run their own OneLogin against one shared file platform.
Point specific OneLogin groups at the right level of access, so only the right people land in Files.com, with the right permissions.
The way people sign in to Files.com with their OneLogin account. One thing to watch: set the certificate fingerprint to SHA-256 — OneLogin defaults to the older SHA-1, and Files.com uses SHA-256.
Turn this on for automatic create, update, remove, and group sync — including cutting off leavers on their own.
Nothing extra to set up — this is what happens when account sync (SCIM) is off. Accounts are created the first time someone signs in. Good for getting started fast; because it can't remove people, use SCIM when you need leavers cut off automatically.
Someone clicks Sign in with OneLogin on the Files.com login page, logs in, and they are in — the same account they use across your apps.
Add a person to a OneLogin group. Files.com creates their account, gives them that group's folders, and sets their admin level — no manual setup.
Turn off a departing employee in OneLogin and the next sync turns off their Files.com account everywhere. This only affects the account that was synced from OneLogin in the first place.
OneLogin asks your own people for a second factor (MFA). Outside partner accounts created in Files.com are required to use Files.com's second factor (2FA), which holds over SFTP.
The folder permissions your OneLogin groups map into — nine levels of access per folder.
Learn MoreEvery OneLogin sign-in and account sync 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 a OneLogin user signs into.
Learn MoreRules that decide how long files stick around once a OneLogin user has put them in Files.com.
Learn MoreWhat buyers ask about how Files.com connects to OneLogin, what it costs, and what the integration actually does.
Start a free 7-day trial. Connect OneLogin to Files.com over SAML, turn on account sync, and prove sign-in-controlled file access on your own workload. No credit card required.
No credit card required • 7-day free trial • Setup in minutes