How Should I Share Files With Clients Without Losing Them in Email?

"Can you resend the latest version?" is not a file-storage problem. It is a source-of-truth problem. Email has as many copies as there are people on the thread, and none of them is labeled in a way a client will remember in three months.

One place the client is allowed to look

Contracts, invoices, and finished deliverables should live on the client record and, when you choose, in Workspace. The portal is not a dump of your entire drive. It is the curated set you would be comfortable with them bookmarking. Internal drafts, pricing notes, and half-finished boards stay in Studio.

Attach files to the work, not to the inbox

A file on a project task with a due date is findable. A file named FINAL_v7_really.pdf in a thread from March is not. Projects let you mark what the client can see per item so you are not maintaining a second, sanitized folder by hand.

Replace "I'll email it" in your own habits

When a deliverable is done, upload it once, share the portal or the task, and mention that location in your note. The first few times this feels slower than attaching. By month three you stop searching Sent Mail for someone else's brand guidelines.

Versioning without a lecture

You do not need enterprise DAM. You need a rule: the portal shows the current signed contract and the current invoice; superseded files are archived or clearly marked. If two PDFs could plausibly both be "the" proposal, the client will pick the wrong one.

Security is mostly access control

A branded portal with an invite is a different promise than a public link that anyone who forwarded the email can open. You still should not put highly sensitive materials in a tool you have not reviewed — but scattering the same files across personal Dropbox, WhatsApp, and email is usually worse, not better. Keep unpublished files in Studio. For the trust side of this, see what a branded portal actually changes.