How to Share Sensitive Client Documents

The most secure method for sharing sensitive client documents is a dedicated client portal: each client gets their own login, files are encrypted at rest and in transit, every download is logged, and you can revoke access when the engagement ends. Email attachments, shared folders, and one-time transfer links each leave a gap. This guide compares all four and sets the minimum bar every professional firm should clear.

What does 'secure enough' mean for client documents?

Three requirements cover most professional use cases: encryption in transit and at rest, per-client access control (client A cannot see client B's files), and an audit trail that records who accessed what and when. A fourth is often skipped: revocable access -- the ability to cut off a client's login when the relationship ends.

The IRS dedicates Publication 4557 (Safeguarding Taxpayer Data) to this topic, recommending that tax professionals use a secure, encrypted portal to transfer client documents and treat unencrypted email as a risk factor. NIST Special Publication 800-111 (November 2007) is the foundational technical reference on storage encryption that most data security frameworks cite.

Email attachments

Email encrypts messages in transit (TLS is now standard), but once the attachment reaches the inbox it becomes an uncontrolled copy. You cannot revoke it, you do not know if it was opened, and the recipient can forward it to anyone without your knowledge.

• No revocation: the file is a permanent copy in the recipient's inbox
• No audit trail: no record of whether the file was opened, when, or by whom
• Forwarding risk: the recipient can share the attachment with anyone
• Inbox persistence: the file lives in multiple inboxes with no expiry

For a routine invoice, email is often fine. For a tax return, a signed contract, or a case file containing personal data, these gaps matter -- see how email and a client portal compare for a fuller look.

Shared Drive and Dropbox folders

Shared folders keep files in one place and encrypt them at rest and in transit. The weak point is per-client isolation: most platforms do not separate clients from each other by default. You build the structure yourself with folder permissions, and one misconfigured share can expose one client's files to another.

Audit logs exist on most platforms, but they are not built for per-client reporting. Generating a record of who downloaded a specific file -- for a compliance request or an IRS audit -- typically requires manually filtering an admin panel, and that log only captures what happened in the folder, not what the recipient did with the file afterward.

One-time transfer links

Transfer links work well for a single large delivery -- a photographer handing off a finished gallery, an agency delivering a completed project. For ongoing client relationships they fall short: links expire (typically 7 days on free plans), there is no persistent client space, and the audit trail is a download count, not a named record of who accessed the file.

There is also no revocation before expiry. If you send a link to the wrong email address, your only options are waiting for the link to expire or contacting the platform's support -- which is not always possible in time. See what to do when you send a file to the wrong person if it has already happened.

Client portals

A client portal creates a dedicated, branded space for each client, accessible only with their own login. Every file action is logged. You can revoke a client's access at any time. For professional firms that exchange documents with clients every week, a portal removes the main failure modes of the other three methods.

ProjectSend Cloud encrypts all files at rest and in transit on every plan. Each paying subscriber gets a dedicated database -- client A cannot see client B's files. The Business plan adds enforced 2FA for staff and lets you export the full audit log to CSV. The software is open-source (GPLv2), so the exit is always open: move back to a self-hosted install at any time and take your data with you. Check plan details and the security overview for a full breakdown.

The four methods compared

• Email: encrypted in transit, but uncontrolled copies, no revocation, no audit trail
• Shared folders: encrypted, but per-client isolation requires manual setup; limited audit trail
• Transfer links: encrypted, but expire, no client account, download count only, no revocation
• Client portal: encrypted at rest and in transit, per-client isolated space, full named audit trail, revocable access

The minimum security bar

Any method you choose should provide, at minimum: encryption in transit and at rest, a named record of who accessed each file, and a way to cut off access when needed. A shared folder can meet the first requirement but rarely the other two. A client portal is designed for all three.

If you handle documents subject to data protection obligations, your clients may also ask for a formal data agreement. See what a DPA is and why clients ask for one. For more on protecting client data, browse the Security & privacy category.