Client files
Every client's files, finally organized
A real drive per client — private, internal and client-shared spaces, folders, brand assets and an activity trail — connected to the projects and meetings the files support. Sign in to your files, or see how it works.
Client files
Agency files end up scattered across personal drives, email attachments and a shared folder no one trusts is current. The Files workspace in AI Marketing Dashboard gives every client its own organized drive inside the console — a private space for works in progress, an internal space for the team, and a clean shared space for what the client should see — so the right file is always in the right place, next to the work it belongs to.
Switch to a client and you see that account's drive, split into a personal space for your own works in progress, an internal space the whole team can use, and a shared space for deliverables the client can see. The three-space model means a draft is never one misclick away from a client, and there is no mental overhead deciding 'where does this go'.
Because the drives are per client, files never blur across accounts. The Files tool guards the all-clients view deliberately — files are a per-client drive, so it prompts you to pick a client rather than fabricating a meaningless merged folder — keeping every account's documents firmly in their own lane.
Create nested folders, upload files, move things around, and open any file into a detail drawer for its metadata and activity. Ordering stays stable, so a file you upload today is in the same place tomorrow rather than reshuffling on reload — the small reliability detail that decides whether a team actually trusts a shared drive.
A live storage indicator reflects what is actually stored — a real file-and-usage count, not a decorative number — so you always know where an account stands at a glance.
Brand assets uploaded during a client's brand intake — logos, guideline documents and the like — surface automatically in that client's internal Design / Brand Guidelines folder, so the team designing for the account always has the source files at hand instead of asking around for the latest logo.
It connects the place you capture a brand to the place you use it, which is precisely the handoff that usually breaks. The newest brand material is where the work happens, not buried in an old email thread.
Every meaningful action on the drive is logged, so a folder is not a black box — you can see what was added or moved and keep a sense of how an account's files have evolved. For an agency juggling many hands on many accounts, that accountability is what keeps a shared drive from quietly drifting into chaos.
It is lightweight by design: enough of a record to answer 'what happened here?' without turning file management into a compliance project.
The client's shared files show up in the meeting hub's workspace rail, can be referenced from a chat message, and live alongside the projects the work is tracked in — so a file is part of the workflow, not a destination you leave the workflow to visit.
That connection is the whole point of keeping files inside the console instead of a generic cloud drive: the document and the work it supports are never more than a click apart.
