Files.com checks each login against Active Directory, or any LDAP directory, right at sign-in. It uses the same password behind Windows logins and network drives, with nothing copied into a second store. And that password works over SFTP, FTP, WebDAV, the Desktop App, mobile, and the API, not just the browser.
At companies that run Windows, Active Directory is the one place that holds everyone's passwords and groups. Files.com checks logins against it, and against any LDAP directory, directly. So people sign in to file transfer with the same login they type for Windows, and you manage one set of accounts instead of two.
Files.com checks each login against Active Directory, or any LDAP directory, right at sign-in. It uses the same username and password behind Windows logins and network drives. Nothing is copied or synced into a second password store, so there's no extra password for people to forget and nothing for you to keep in sync.
This is the big one. With AD or LDAP, the same directory password works over the website, FTP, SFTP, WebDAV, the Desktop App, mobile, and the API. Not just the browser. Cloud sign-in services can't do that, so a partner connecting over SFTP uses their company login like everyone else, and you never hand out a second key or password to manage. It's the main reason teams pick LDAP.
Remove someone from Active Directory and they lose Files.com access the same way they lose every other company login. There's no separate list to remember, so a departing employee can't keep file access you forgot to revoke, and your next access review comes back clean.
Say that only members of a certain directory group get Files.com accounts, and let that same group decide which folders they can reach. The access setup already in your directory carries straight through, so you don't rebuild your group structure here, and the right people get the right folders the moment they join the group.
Set a backup directory server and Files.com switches to it on its own when the main one can't be reached. People can still sign in during directory maintenance and outages, so a directory problem doesn't lock your partners out of their file transfers.
Your directory says who someone is. It was never meant to decide which folders they touch, or what they can do once inside a file platform. Files.com adds that part on top of the directory it checks logins against. You get fine-grained folder access, a full record of everything, and a connection built for directories that live behind the firewall.
Set access per person or group, folder by folder. You get nine levels, the option to block a folder, and fenced-off admins. The groups you already have in your directory feed straight into it.
Every sign-in and permission change lands in the Files.com audit log. The hourly directory sync is recorded too. That’s the history a SOC 2 review or an access dispute asks for.
Files.com connects with a read-only account limited to the parts of the directory you pick, and uses a secure, encrypted connection (LDAPS) so passwords are never sent in the clear. Read-only means Files.com can check a login but can't change anything in your directory, which is the answer your security team asks for before they approve the connection.
Most setups can't reach an internal-only directory. Files.com can. Add its published IPs to your firewall's allow-list, or run a small Files.com Agent inside your network that reaches the directory for you. The directory never gets exposed to the internet, so you get directory sign-in without opening your internal directory to the outside world.
The directory password works over the website, FTP, SFTP, WebDAV, the Desktop App, mobile, and the API. Company credentials work over the file-transfer protocols, not just the browser. No cloud sign-in service can do that.
Set a backup directory server and Files.com switches to it on its own when the main one can't be reached, so people can still sign in during directory maintenance and outages.
Every login is checked against the live directory right then, so a password change or a disabled account takes effect at the very next sign-in. There's no sync to wait on, so the moment you disable an account in your directory, that person is locked out of Files.com too.
Pick Active Directory/LDAP in Files.com and point it at your directory. You give it the server address, a read-only account, and which part of the directory to search, so setup is a short form, not a project. Use this when the same password has to work over the file-transfer protocols, not just the browser. Works with on-premises and hybrid directories.
If the directory sits behind the firewall and you'd rather not open it to the internet, run a small Files.com Agent inside your network. It reaches the directory from inside, so the directory server never needs an open inbound port.
When you move the directory to the cloud, run Entra ID alongside LDAP, switch people over one at a time, and turn off LDAP once everyone's moved. No flag day, no lockout.
A person connects over SFTP with their Active Directory username and password, the same one they use for Windows. There's no separate Files.com password or key to hand out, so there's one less credential to support and one less to leak. The directory checks the SFTP login, not just the browser one.
Only members of a chosen directory group get Files.com accounts, and that group also decides which folders they can reach. Add a person to the group in your directory and their Files.com account and folders are set, so onboarding a new hire is one step, not a separate ticket for the file platform.
The main directory server goes offline for maintenance, Files.com switches to the backup, and people keep signing in without a break.
A company moving from on-premises Active Directory to Entra ID runs Entra alongside LDAP, tests one person, moves the rest, then turns off LDAP. No flag day, no lockout.
The folder-by-folder access, with nine levels, that your directory groups feed into.
Learn MoreWhere every sign-in and permission change is recorded, ready to export for a compliance review.
Learn MoreHow 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 MoreNovember 17–20, 2026 · San Francisco, CA
Files.com builds deeply on SharePoint, OneDrive, Azure, and Microsoft Entra ID, so of course we’ll be on the floor at Microsoft Ignite telling our File Orchestration story. The legacy MFT vendors won’t be there.
See Files.com At Microsoft Ignite
Common questions about how Files.com connects to Active Directory / LDAP and what the integration actually does.
Start a free 7-day trial. Point Files.com at your directory, log in with a corporate account over the browser and over SFTP, and prove directory authentication works on your environment. No credit card required.
No credit card required • 7-day free trial • Setup in minutes