How to organize files across multiple clients

The typical multi-client file system starts well. You create a folder per client, maybe nest a few subfolders for deliverables and briefs, and for a while everything has a place. Then one client's scope expands. Another sends files across three different platforms. A teammate saves something to the wrong directory. Within a few months the structure has drifted, search turns up nothing useful, and half the team has built private workarounds in their own cloud storage.

The problem is rarely a lack of discipline. It is that most file systems are static containers. They hold things, but they do not understand what is inside them, who needs access, or how the work connects across clients. Fabric approaches this differently: it serves as a persistent memory and context layer that sits across all your tools and content, giving you a single vault where every client file, conversation, and deliverable is organised, searchable, and accessible, whether you are working in Fabric itself or through an AI assistant like ChatGPT or Claude.

This guide walks through a practical system for agencies, freelancers, and consultancies managing files across multiple clients using Fabric's folder structure, spaces, tags, kanban views, and cloud drive.

Start with one folder per client

The foundation is simple: create a top-level folder for each client. Inside that, build a consistent subfolder structure you replicate across every client. A common pattern might be Briefs, Deliverables, Assets, Contracts, and Communications. The specific names matter less than the consistency. When every client folder follows the same template, anyone on the team can step into an unfamiliar project and find what they need without asking.

Fabric's folder-based organisation supports this nesting naturally, but it goes further than a conventional file tree. Because Fabric functions as a unified vault for all your connected tools, the folders you create are not just holding local files. They can contain items pulled from Google Drive, Dropbox, Notion, Slack, Gmail, and more than 50 other connections. A brief that arrived in Gmail, a design file stored in Dropbox, and meeting notes from Notion can all live inside the same client folder without moving the originals. Fabric indexes and organises them in place.

This means you do not need to coerce everyone into a single storage platform. Each team member (or each client) can continue using whatever tools they prefer. Fabric brings the structure to the content, regardless of where it lives.

Use spaces for team-level grouping

If you run an agency with distinct departments or service lines, folders alone can become unwieldy once you pass a dozen clients. Spaces in Fabric let you create higher-level groupings: a space for each team, department, or practice area. Within each space, the per-client folder structure stays the same, but the space boundary keeps things tidy and controls who sees what.

A design agency might have a Branding space and a Web Development space, each with its own set of client folders. A consultancy might organise by region or by engagement type. Spaces also make collaboration cleaner. Rather than managing permissions folder by folder, you can set access at the space level and override where needed. Each space becomes a self-contained working environment for the people who need it.

Layer in tags for cross-cutting views

Folders give you a per-client view. Tags give you a cross-client view. This distinction is worth spending a moment on, because it solves one of the more persistent headaches in multi-client file management: finding everything related to a particular topic, deliverable type, or status across all clients at once.

For example, you might tag certain files with "proposal", "final-deliverable", "awaiting-feedback", or "Q4-2026". Those tags let you pull up every outstanding proposal across all clients, or every final deliverable submitted in a given quarter, without navigating into each client folder individually. Tags in Fabric work across your entire vault, so they span folders, spaces, and even connected tools.

A useful starting point is to maintain two or three tag categories: one for deliverable type (proposal, report, creative brief), one for status (draft, in-review, approved), and one for time period or project phase. Keep the list short enough that people use it consistently. A tag system with fifty options is a tag system no one uses.

Track deliverables with kanban views

Once you have tagged your files by status, Fabric's kanban views let you visualise them as cards on a board. Each column represents a status (such as To Do, In Progress, In Review, Complete), and each card is a file or deliverable. You can filter the board by client, by tag, or by team member.

This is particularly useful for agencies juggling multiple active engagements. Rather than maintaining a separate project tracker in another tool, the kanban view pulls directly from your file system. When a deliverable moves from draft to review, updating its position on the board also updates its tag. The file, the metadata, and the status all stay in sync because they are all part of the same system.

For freelancers managing a handful of clients, a single kanban board filtered by client can replace a spreadsheet tracker entirely. For larger teams, boards per space or per department keep the view manageable without losing the ability to zoom out across all active work.

Eliminate local storage with Fabric's cloud drive

One of the quieter problems with multi-client file management is storage. Design assets, video files, large document sets: these accumulate quickly, and syncing them across machines creates version conflicts and eats disk space. Fabric's cloud drive sidesteps this entirely. Files are stored in the cloud with zero local footprint and streamed on demand when you open them.

This is not a sync-and-cache model. The files do not sit on your hard drive waiting to be opened. They exist in Fabric's vault and are available instantly when needed. For agencies working with large media libraries or consultancies managing thousands of documents across dozens of clients, this removes a meaningful operational headache. There is no "my laptop ran out of space" problem, no version drift between machines, and no risk of a team member accidentally deleting a local copy.

The cloud drive also means that onboarding a new team member does not require syncing gigabytes of client files to their device. They get access through Fabric, and every file is available immediately, streamed rather than downloaded.

Set permissions so clients see only their own files

Multi-client environments require careful access control. A client should see their own deliverables and nothing else. A junior team member might need access to three clients but not the contracts folder. Fabric supports granular permissions at the folder and file level, with roles for viewer, commenter, editor, and admin.

The practical approach is to give each client access to only their folder, and to limit team members to specific client folders based on their role. If you want to go further, Fabric supports setting up a client portal where external stakeholders can view, comment on, or download files without ever seeing the rest of your workspace. All of this is protected by AES-256 encryption and CASA Tier 2 security standards, which matters when you are handling contracts, financial data, or pre-release creative work.

Let the memory engine connect the dots

What separates Fabric from a conventional file organiser is the Exabase M-1 memory engine, which scored first on LongMemEval with 96.4% accuracy. This is not a search index. It is a system that understands the relationships between your content: which files relate to which clients, which conversations led to which deliverables, which decisions were made and when.

When you search across your vault, the results are semantic, not just keyword-based. Searching for "the budget we discussed with Meridian in August" will surface the relevant spreadsheet, the Slack thread where the numbers were debated, and the email where the final figure was confirmed. This works across all connected tools and all client folders.

For multi-client environments, this means that institutional knowledge does not evaporate when a project ends or a team member leaves. The memory engine retains the context, the connections, and the history. Six months later, when the client comes back for a new engagement, everything is still there, linked and searchable.

Fabric also generates self-writing documentation from your content. A client relationship tracker, for example, can assemble itself from meeting notes, emails, deliverables, and tagged milestones. Rather than manually maintaining a CRM-style document for each client, the system keeps a living summary that updates as new content arrives.

Access your files from any AI assistant

One of Fabric's more distinctive capabilities is that your vault is not locked inside a single interface. Through Fabric's MCP integration, you can access your files, memories, and connected tools from within AI assistants like ChatGPT or Claude. If you are drafting a proposal in Claude and need to reference a client's past deliverables, you can pull them in directly from Fabric without switching windows.

For agencies and consultancies, this means your file system becomes part of your AI workflow rather than a separate silo you alt-tab into. You can ask an AI assistant to summarise a client's project history, find the most recent version of a contract, or compare deliverables across two clients, all drawing from the same organised vault you have built in Fabric.

Fabric also supports scoped agent access: you can approve an AI agent for limited-time access to a specific set of tools or folders. This keeps things controlled. An agent helping with a particular client engagement gets access to that client's files and nothing more, and the access expires when the task is done.

A practical setup checklist

For agencies and freelancers getting started, the sequence is roughly this. First, connect your existing tools (Google Drive, Dropbox, Slack, email, and whatever else your team uses). Second, create a top-level folder per client with a consistent subfolder template. Third, set up spaces if you have multiple teams or departments. Fourth, agree on a short list of tags for deliverable types and statuses. Fifth, build a kanban board or two for tracking active work. Sixth, set permissions so each client and team member sees only what they should. Seventh, enable the cloud drive for any team members who are running low on local storage or who work across multiple devices.

The whole setup takes an afternoon for a small team, perhaps a day for a larger agency. The payoff is a file system that scales with you, that understands your content rather than just storing it, and that stays organised as clients come and go.

Frequently asked questions

How do I keep folder structures consistent across all clients?

Create a template folder with your standard subfolders (Briefs, Deliverables, Assets, Contracts, Communications, or whatever fits your workflow) and replicate it each time you onboard a new client. Fabric's folder system makes it simple to duplicate structures. The key is agreeing on the template as a team and sticking to it.

Can I connect files from Google Drive, Dropbox, and other tools without moving them?

Yes. Fabric supports more than 50 connections, including Google Drive, Dropbox, Notion, Slack, and Gmail. Files stay in their original location. Fabric indexes and organises them within your vault so they appear alongside everything else in your client folders.

How do tags work across multiple client folders?

Tags in Fabric are global. A tag like "proposal" or "awaiting-feedback" applies across your entire vault, so you can filter by that tag to see every matching file across all clients and all connected tools. This gives you cross-client views without duplicating files or maintaining separate trackers.

What permissions can I set for external clients?

Fabric supports four permission levels: viewer, commenter, editor, and admin. You can set these at the folder or file level. For external clients, the typical approach is to share a specific folder (or a curated client portal) with viewer or commenter access, keeping everything else invisible to them.

Does the cloud drive replace local file storage entirely?

It can. Fabric's cloud drive stores files with zero local footprint and streams them on demand. You do not need to sync or download files to access them. For teams dealing with large asset libraries, this removes storage constraints and version-sync issues entirely.

How does semantic search differ from regular file search?

Regular search matches keywords in file names and content. Fabric's semantic search understands meaning and relationships. You can search for a concept, a topic discussed in a meeting, or a decision made in an email thread, and the engine will surface relevant results even if the exact keywords do not appear in the file name.

Can I use Fabric's files from ChatGPT or Claude?

Yes. Through Fabric's MCP integration, your vault is accessible from within AI assistants like ChatGPT and Claude. You can reference client files, pull in past deliverables, or search your vault without leaving the AI interface. Agent access can also be scoped to specific folders and given time-limited permissions.

How does the self-writing documentation feature work for client management?

Fabric's memory engine assembles documentation from your existing content: meeting notes, emails, deliverables, and tagged items. A client relationship tracker, for instance, updates itself as new content arrives. You do not need to maintain it manually. The system infers the structure from what it knows about the client and the project history.

Is my client data secure in Fabric?

Fabric uses AES-256 encryption and holds CASA Tier 2 certification. Permissions are granular, so you control exactly who can see, comment on, or edit each file and folder. For agencies handling sensitive client information, this meets the bar for most enterprise and regulatory requirements.

How long does it take to set up a multi-client workspace?

For a small team or solo freelancer, an afternoon is usually enough to connect tools, create client folders, set up tags, and configure permissions. Larger agencies with multiple departments and dozens of clients might spend a full day on the initial setup, with refinements over the following week as the team settles into the workflow.

Related pages

• How to give a client access to only their files

• How to limit team members to specific client folders

• How to set up a client portal

• How to manage multiple clients

• Fabric for agencies

• Fabric for freelancers