Shared Folders Are Not a Workflow

When a marketing agency "sets up client access," the most common approach is to share a Google Drive folder. The client can see everything in the folder. Done.

This feels like a workflow. It isn't. It's storage access — a necessary component of a workflow, but not the workflow itself.

What a Workflow Actually Requires

A deliverable management workflow needs to answer six questions:

1. Who can access which documents? (Not just "the client folder" — specific documents for specific reasons at specific times)
2. What does the client experience when they access their deliverables? (A raw Drive folder or an organised, branded workspace?)
3. When does the client receive notification that something is ready? (Do they need to check the folder regularly, or are they proactively informed?)
4. How does the client provide feedback or approval? (Comment on Drive? Email? Meeting?)
5. What happens to access when the engagement ends? (Stays forever? Gets revoked? Converted to read-only archive?)
6. What can the team see about client engagement? (Did they open it? Which sections? How long?)

A shared Google Drive folder answers question 1 (sort of) and nothing else.

The Three Gaps Between Folder-Sharing and Workflow

Gap 1: No curated delivery experience. A shared folder is the client's view into your internal organisation. If your folder structure makes sense to you, it probably doesn't make sense to them — and they certainly don't want to see your work-in-progress files, internal drafts, and admin documents alongside the polished deliverables.

Gap 2: No engagement lifecycle. A shared folder doesn't have a beginning, middle, and end. Once shared, it just continues. There's no "milestone delivered" moment, no "engagement wrapping up" state, no "here's your archive" close.

Gap 3: No visibility. You don't know whether the client has opened the folder. You don't know which files they've looked at. You have no signal about whether they've engaged with your work.

What to Use Instead

A client portal — built on top of your Google Drive storage — addresses all three gaps. The client sees a curated, branded workspace rather than a raw folder view. The portal has lifecycle states (active, wrapping, archived). And you have analytics showing who accessed what and when.

Critically, moving to a portal doesn't mean moving your files. Tools like Firma layer on top of Google Drive — your files stay where they are, and the portal provides the interface, the access control, and the delivery experience on top.

---

Frequently Asked Questions

What is the difference between a shared Drive folder and a client portal?

A shared Drive folder is storage access — the client can see your files. A client portal is a structured delivery experience — the client sees a curated, branded workspace with controlled access, delivery notifications, engagement analytics, and a defined lifecycle. A portal is built on top of storage, not a replacement for it.

Can I build a client portal workflow on top of Google Drive without moving my files?

Yes. Tools like Firma are specifically designed to create portal-layer experiences on top of existing Google Drive storage. Your files stay in Drive; the portal handles the client-facing interface, access control, and engagement management.

Why do marketing agencies default to shared folders instead of proper portals?

Shared folders are the path of least resistance — they require no setup, no configuration, and no new tools. The costs are hidden and accrue over time. Portals require initial setup but generate ongoing returns in client experience, IP protection, and operational clarity.