The Folder That Never Got Closed
A designer runs a routine audit of their cloud storage and finds nineteen shared folders. Six belong to clients whose projects ended more than a year ago, and two of those clients are now working with a competitor.
Nobody did anything wrong. Every folder was shared for a good reason, and closing a project simply never included a step for unsharing it.
That is the real question behind portals and shared drives. Both move files from you to a client, and they differ almost entirely in what happens after the work is done.
What Actually Breaks in a Shared Folder
Delivery is the easy part, and every tool handles it. The problems cluster at the edges of a project rather than the middle.
Access outlives the engagement by default. A shared link stays live until somebody remembers it, and remembering is a task that competes with billable work.
Approvals leak into other channels. The client says the third version looks great in a chat thread, then asks in a call for a change to the version they approved, and the record of that approval is nowhere near the file.
Version identity gets murky fast. Final, final revised and final v3 are a running joke because dated filenames are how humans compensate for a system that does not track intent.
Scope creep hides in the same gap. Without a timestamped approval, a request that arrives after sign-off looks identical to a request that arrived before it.
What a Portal Adds Beyond Storage
A client portal is a folder wrapped in workflow. The storage layer is often the same underneath, and the difference lies in what surrounds the files.
Approval states come first. A portal lets a client mark a deliverable as approved, which converts a conversation into a record you can point at three months later.
Scoped access comes second. A portal shows each client only their own space, so adding a new client does not mean building another folder tree and hoping the permissions are right.
Offboarding becomes one action instead of an audit. Archiving a client closes their access to everything at once, which is the specific failure that folder-based delivery keeps producing.
Presentation matters more than people admit. A branded space where a client logs in reads differently from a link to a folder, particularly at the price points where clients expect a studio rather than a freelancer.
Five Delivery Setups Compared
The table maps the realistic options rather than the marketing categories. Confirm current pricing on each vendor’s official site, since plans in this category change frequently and seat definitions vary.
| Setup | Typical examples | Offboarding effort | Approval record | Fits |
|---|---|---|---|---|
| Shared cloud folder | Google Drive, Dropbox, OneDrive | Manual, per folder | None built in | Up to a few concurrent clients |
| Folder plus naming rules | Any drive with a written convention | Manual but predictable | Filename conventions only | Solo work with steady process |
| Client view in your PM tool | Asana, ClickUp, Notion guest access | Remove guest, one action | Task status as proxy | Teams already living in one tool |
| Dedicated client portal | Purpose-built portal products | Archive client, one action | Explicit approval states | Studios with recurring clients |
| Portal plus e-signature | Portal paired with a signing tool | Archive plus signed record | Signed, timestamped | Contract-heavy or regulated work |
Notice that the cost column is missing on purpose. The deciding factor is almost never the subscription price, because the middle rows are frequently included in tools a team already pays for.
The Option Most People Overlook
Before comparing portal products, check what your current stack already does. Guest or client access is a standard feature in most project management tools, and many invoicing platforms include a client-facing area.
That path avoids a new subscription, a new login for the client, and a new place for files to sit. It also keeps delivery next to the tasks and invoices, which is where questions about a deliverable usually start.
The limitation is presentation and granularity. Guest access tends to show a tool’s native interface rather than your brand, and permissions are often coarser than a dedicated portal offers.
Try that route first if you already run a tool with guest seats. Auditing what you pay for before adding to it is the same discipline that keeps a stack from bloating, and it applies here as much as it does when you audit SaaS subscriptions.
Five Settings Worth Fixing Today
Whichever route you take, a handful of configuration choices cause most of the trouble. They take an afternoon to fix and prevent the failures that force a migration later.
Turn off open link sharing as a default. Anyone with the link is convenient for a one-off transfer and dangerous as a standing policy, because links get forwarded and indexed in ways you never see.
Set expiry dates when the tool supports them. A link that dies on its own is the only form of access revocation that does not depend on somebody remembering.
Separate working files from delivered files. Clients who can see the messy middle will comment on the messy middle, and the confusion costs more time than a second folder does.
Decide who owns the account before the first client, not during a staffing change. Client files sitting under a personal login are an unnecessary risk, and the fix costs five minutes at signup rather than a support ticket later.
Write the close-out steps into a checklist you actually run. Unshare, archive, export the final files, and note where they went. Delivery tools change over the years, and the archive should outlive the subscription.
What Clients Complain About
Vendor comparisons rarely mention the complaint that ends portal experiments. Clients dislike creating another account for a relationship that may last six weeks.
That friction is real and it is worth pricing into the decision. A portal the client never opens is worse than a folder, because the work is now somewhere neither party checks.
Look for magic-link or guest access that skips password creation. This one detail separates portals that clients adopt from portals that quietly become your own private filing system.
Ask a client directly before you switch. Most will tell you plainly whether a login is a problem, and their answer beats any feature comparison you can read.
Which Setup Fits Your Client Load
You handle two or three clients at a time: stay with a shared folder and add one habit. Put an unshare step in your project close checklist, and the main risk disappears without any new software.
You run six or more concurrent clients: move to client-scoped access in a tool you already own. The volume of folders is what turns manual permission management into a reliable source of mistakes.
Your work needs written approvals: choose a portal with explicit approval states, or pair delivery with a signing tool. Design, marketing and consulting all live or die on the question of what was signed off and when.
You work with regulated or sensitive material: a portal with audit logs stops being optional. Legal, healthcare and financial clients frequently ask how access is controlled, and folder sharing is a difficult answer to give well.
You subcontract parts of the work: separate the client space from the production space. Contractors need access to files, not to your client relationships, a boundary that also affects whether contractors need paid seats.
You bill hourly and delivery is simple: skip the portal entirely. A folder plus an invoice covers it, and the time spent configuring a portal is time you could bill.
Migration Costs Nobody Budgets
Moving delivery from folders to a portal looks like a weekend task and rarely is. Historical files are the first surprise, since years of past work do not map cleanly onto a client-by-client structure.
Client habits are the second. People who have received links for three years will keep asking for links, and a portal only works if the client actually logs in.
Plan the transition around new projects rather than old ones. Start the next engagement in the portal, leave completed work where it sits, and archive the old folders on a schedule instead of migrating them.
Budget for the login problem too. Every portal adds a credential the client must keep, and the tools that survive in practice are the ones that make that step nearly invisible.
The Decision in One Line
If your delivery problem is storage, a folder already solved it. If your delivery problem is proof of what was agreed, no amount of folder discipline will solve that.
Most freelancers reach the second problem later than they expect and address it earlier than they need to. The useful trigger is not client count but the first dispute about what was approved.
Approval is that same problem in miniature. Once you need a record of what a client agreed to, a signature tool settles it faster than any folder convention. Our comparison of an e-signature tool against free PDF signing marks where the free route stops being enough.
FAQ
Is a shared Google Drive folder good enough for delivering client work?
A shared folder works until the client roster grows past a handful or someone leaves. The failure is rarely dramatic. It shows up as a client who still has access a year after the project ended, or a file version nobody can identify as final.
What happens to client access when a project ends?
Revoking access to a whole folder is simple, but revoking access to copies is impossible. Anyone with view rights can download, and files already synced to a laptop stay there regardless of what you change later.
Do you need a dedicated portal tool, or can an existing tool cover it?
Yes, for most freelancers and small studios. Many project management and invoicing tools include a client-facing view, so a separate portal subscription is often unnecessary until you need branded delivery or signed approvals.
When is a client portal actually worth the extra cost?
Portals help when you must show who approved what and when. A shared drive records file edits, not decisions, so an approval given in a chat message lives outside the system where the work does.
Should client files ever sit in a personal cloud account?
Rarely a good idea. Client documents that live in one person's personal account travel with that person, and recovering them later means a support ticket, proof of ownership, and an uncomfortable conversation.
Some links may be affiliate links. We may earn a commission at no extra cost to you.
This article was written with AI assistance. It is researched and fact-checked, not based on personal hands-on testing unless explicitly stated.
Comments
Post a Comment