In A Folder Only The Right Staff See
Uploads land in a write-only intake folder per department, per case, or per client. Folder permissions decide who can open it, and the audit log records every access after that.
Collect Documents From Clients And Vendors Without Creating Accounts
Files.com gives every sender a branded page or link they open in a browser, and lands each file in a folder only the right staff can see, with the sender identified, the team notified, and the file routed onward or expired on schedule. Clients, patients, students, vendors, bidders, and new hires submit without an account.
Email gateways block the attachment. Consumer tools expose someone else’s files. A login provisioned for every person who submits once caps your intake at the size of the team administering accounts.
No account for the sender
Every submission private to its sender
Routed to your system of record
The People Who Send You Documents Are Not Your Users
An applicant sends a transcript once. A patient uploads an insurance card once a year. A vendor submits a tax form, a bidder a proposal, a new hire an onboarding packet. None of them will ever log in again, and every one of them is handing you something sensitive.
Handled through email, the gateway blocks it or it scatters across mailboxes. Handled through a consumer tool, the wrong sender sees the wrong files. Handled through accounts, intake stops at the size of the team creating them. On Files.com the sender gets a page, the file gets a folder only your staff can open, and the record of who sent what writes itself.
4,000+ organizations rely on Files.com every day
Real companies. Real file flows. Real results.
How The Intake Runs
A page the sender can use, a form that files the document, a notification the moment it lands, and an expiry when the case is done.
A Branded Page They Open In A Browser
An Inbox is a permanent upload page under your own domain, or an email address that accepts attachments. The sender drags files in and submits. No account, no software, nothing to install on a phone.
The Sender Identified, The File Filed
A custom form asks for the fields the workflow needs, a name, a case number, a department, before the upload, and the answers route the file into the right subfolder. Each submission is private to its sender, so a hundred applicants use one page and none of them can see another’s paperwork.
The Team Told The Moment It Lands
A notification emails the owning team, or a webhook tells your case system, when a file arrives. Nobody watches a folder, and the sender can receive a branded receipt confirming what was received.
Terms Accepted, Files Expired
A clickwrap agreement records acceptance of your terms, with timestamp and IP, before the upload. Retention rules expire the file once the case is closed, so an intake page never becomes an archive of documents nobody meant to keep.
Where The Documents Land
The upload page is the front door. The file lives wherever your staff and systems already look.
In Your Own Storage Or System Of Record
A mount or sync lands each submission in SharePoint, your cloud bucket, or an on-premises share, and an Automation or webhook attaches it to the record in your CRM, ERP, or practice-management system.
Created From Your Own Workflow
The REST API mints a per-case upload link from inside your application, so a case opened in your system carries its own intake page and retires it when the case closes.
Customers Collecting Documents Through Files.com
Porsche Cars North America Built a Files.com Alternative to Email and FileZilla That Teams Adopted Without Promotion
To clear Porsche AG's hosting rules, the channel combined federated identity, Porsche branding, and Canadian data residency for workflows across the business.
Read The Story
Spanx Collects Traceability Documentation From 90+ Suppliers on Files.com With Zero External Accounts
Supplier-specific upload pages capture style numbers with each file, then move every submission into SharePoint and delete it from the external site within five minutes.
Read The Story
Transtron America Replaced Email Transfers with Files.com—Without Opening Fujitsu’s Network
A four-person operation with no IT staff built an upload-only Files.com exchange for sensitive files from its third-party warehouse.
Read The Story
Orica Keeps File Exchange Stable Through a Global Payroll Replacement With Files.com
A durable Files.com hub gave SAP, payroll providers, and vendors a governed exchange point that could outlast the systems around it.
Read The Story
“I set up all our users and set up inboxes where our customers can send us files, and everything just works. Email notifications are also a big thing for us — we need to know when we have a new file sent to us, and those just work as well.”
Lance Phillips
Controller, Gerald Printing
“The one-time file upload links, one-time file download links, and the management UI make my work easier and more efficient — they make it easier to gather and share sensitive documents in a secure way.”
Steven Papadakis
Founder & CEO, NE2NE
How It Compares
The three ways outside documents come in today, and what each one exposes.
Email Attachments And Password-Protected ZIPs
The gateway blocks half of them, the rest scatter across mailboxes, and the password travels in the next email. A tax form or an insurance card sitting in someone’s inbox is exactly what the security review is about.
Consumer Tools And Guest Links
A shared folder in a consumer tool exposes other files to the wrong sender, and a collaboration-suite guest link widens your identity boundary to include every applicant, patient, and vendor who ever sent you a document.
An Account For Every Submitter
Provisioning a login for someone who will upload once, and cleaning it up later, caps intake at the size of the team administering accounts. The people who submit rarely should never need a credential at all.
Document Collection FAQ
What IT, security, HR, finance, and client-services teams ask before moving intake onto Files.com.
Send them a Files.com Inbox: a branded upload page under your own domain that opens in a browser. The client drops files and submits, with no account and no software. Each submission lands in a folder only your staff can see, private to that sender, and your team is notified the moment it arrives.
No. An Inbox is write-only from the outside. Every sender sees only their own submission on the page and nothing that anyone else uploaded, so a single page serves hundreds of applicants, vendors, or patients without any of them reaching another’s paperwork.
Files.com offers a HIPAA Business Associate Agreement, encrypts files at rest and in transit, and logs every access to an immutable audit trail. Clinics and health plans collect insurance cards, records, and enrollment paperwork through branded Inboxes under that agreement, with retention rules that expire files once the record is complete.
Yes. A custom form on the Inbox collects short answers, dates, dropdowns, and multiple-choice fields before the upload, and the answers can name the subfolder the file lands in, so submissions self-organize by applicant, case, or department. A link can pre-fill and lock a field, so a specific partner’s uploads are stamped with their name.
A folder notification emails the owning team when a file lands, branded with your logo, and a webhook can post the arrival to Slack, Teams, or your case-management system. The sender can receive a receipt confirming what was received.
Yes. Each department runs its own Inbox under the company domain, with its own intake folder that only that department’s staff can open. New hires submit onboarding forms and vendors submit tax and banking paperwork through a page instead of email, and retention rules remove the files once they have been processed.
Yes. A Remote Server Mount or sync lands each submission in a SharePoint library, an Amazon S3 or Azure Blob bucket, or an on-premises share, and an Automation or webhook attaches it to the record in your CRM or ERP. The intake page is the front door; the file lives where your systems already look.
Yes. An Inbox can be embedded as an upload form on your public website, intranet, or client portal, so applications, proposals, or evidence are collected on your own page and land in a governed folder behind it. A public form can also carry a custom form and a clickwrap agreement.
Every submission is recorded with the sender’s identity from the form, the time, and the file, and every access to it afterward is in the audit log. Inbox usage reports list what was submitted through which page, so the question of whether a vendor sent its paperwork is a lookup rather than a search through inboxes.
A per-folder retention rule deletes or archives them after the window you set, and an Automation can move a closed case’s files to your system of record first. The intake folder stays lean, and the audit log keeps the record of what was received after the file itself is gone.
Give Every Sender A Page, Keep Every Document Governed
A branded upload page under your domain, a form that files the document, a folder only the right staff can open, and an expiry when the case is done. Start the 7-day free trial and publish your first intake page today.
No credit card required • Free for 7 days • Live in minutes