One Login, No Separate Password
Your team signs in to Files.com with the same Google login they already use for Gmail and Workspace. There's no second password to hand out for file transfer — on the website or in the Desktop App.
Connect Files.com to Google and your Workspace users sign in to file transfer with the Google login they already have — no second password. On top of that login, Files.com sets who can reach which folders and keeps a record of everything that happens.
Google already signs your people in everywhere else they work. Files.com uses that same Google login for file transfer — partner exchange, sending files to people outside the company, taking large files in — so there's no separate password to manage, and the folder controls Drive can't do come from Files.com.
Your team signs in to Files.com with the same Google login they already use for Gmail and Workspace. There's no second password to hand out for file transfer — on the website or in the Desktop App.
Give someone access in Google Workspace and Files.com makes their account the first time they sign in — no setup step in between. (This is called JIT.) They're ready the moment they log in.
Because the account isn't created until someone's first login, you never pay for a person who has Google access but never logs in to Files.com. You pay for people who actually use it.
Set who can reach which folders, keep a record of every file action, put expiration dates on share links, and take large files from people outside your company. This is the control a Workspace admin needs when Drive can't carry a partner or regulated workflow.
Google’s MFA covers the people who sign in through Google. For partners and outside accounts Google doesn’t manage, Files.com adds its own 2FA — including hardware keys and authenticator apps — and it also covers FTP, SFTP, and WebDAV.
Google confirms who is signing in. It was never meant to decide which folders that person can touch, or to record what they do. Files.com adds that part — nine levels of access, per person or group, folder by folder, with every sign-in and permission change in a record you can export.
Nine levels of access, per person or group, folder by folder — with the ability to block a folder and to fence off admins. Each person who signs in with Google reaches exactly the folders they should, and nothing else.
Every sign-in, file action, and permission change is logged and exportable. You get an audit-grade record of document handoffs and share-link activity that Google Drive doesn't keep for partner or regulated exchange.
The Google sign-in uses OAuth/OIDC, so accounts are made on first login (JIT) rather than synced ahead of time. To remove someone, turn off their access in the Google admin console and deactivate them in Files.com — by inactivity rule, expiration date, or by hand.
Require Files.com 2FA — a hardware key or an authenticator app — on partners and outside accounts that don't sign in through Google. That requirement also holds over their FTP, SFTP, and WebDAV connections.
The connection runs on Google's own OAuth 2.0 / OpenID Connect login — the same one Google already trusts for Gmail and Workspace. There's no special connector to build or keep running.
Accounts are made the first time someone signs in with Google, so an approved Workspace user is ready the moment they log in. First-login creation (JIT) can't remove people, though — to off-board, turn them off in Workspace and deactivate them in Files.com.
A Google login covers both the website and the Files.com Desktop App. SFTP, FTP, FTPS, and WebDAV connections keep their own keys or passwords, so partner and machine access stays separate from the people signing in with Google.
Files.com respects the MFA a Workspace admin already requires for the people who sign in through Google, and adds its own 2FA — hardware keys and authenticator apps — for the partners and outside accounts Google never sees.
Pick Google from the sign-in providers in Files.com and save — there's barely anything to set up. Set each person's login method to Google, matching their Google email. From then on they click Log in with Google.
Nothing extra to set up — accounts are made on first Google login. Since first-login creation can't remove people, off-board them in the Google admin console and deactivate them in Files.com (by inactivity rule, expiration date, or by hand).
A Workspace user clicks Sign in with Google on the Files.com login page and lands in their account using their normal Google login — no separate file-transfer password.
A newly approved Google user signs in for the first time, and Files.com makes their account on the spot — already set to the folders and permissions their group carries.
A team on Google Drive uses a Files.com inbox to collect large files from an outside partner who has no Google account — and every handoff is logged. That's the gap Drive leaves.
A partner account that doesn't sign in through Google can be required to use Files.com 2FA, and that holds over their SFTP connection.
Put a GCS bucket behind the same Google login — file access and storage under one sign-in.
Learn MoreConnect Drive as storage and put folder permissions and an audit trail on top of the same Google login.
Learn MoreCollect large files from outside partners who have no Google account, with every handoff logged — the gap Drive leaves.
Learn MoreThe folder-by-folder, nine-level access that sits on top of the Google login.
Learn MoreWhat buyers ask about how Files.com connects to Google, what it costs, and what the integration actually does.
Start a free 7-day trial. Set Google as your sign-in provider, log in with an existing Workspace account, and see it work on your own files. No credit card required.
No credit card required • 7-day free trial • Setup in minutes