Blog

AI agents for agencies: one agent per client, nothing crossing over



How an agency can give each client's AI agent access to that client's folder and nothing else, and hand the work over cleanly when a project ends.



An agency can run AI agents across a dozen clients without one client's files reaching another, as long as each agent is limited to a single client's folder. In Fabric, that means one space per client and one agent per client in Agent Vault, each with access to that client's space and nothing else.

The rest of this post covers how to set it up, what to put in each client's folder, and how to hand work over to a colleague or to the client.


Why client separation matters more once agents join

A strategist working on a dental chain's spring campaign knows not to borrow figures from the bakery account down the hall. That judgment comes from years of client work and a sense of who is paying for what. An agent has none of it. If it can reach the whole drive and you ask for "last year's launch results," it will return whichever file matches best, and that file may belong to a different client.

Most shared drives were set up around staff permissions, and an agent often borrows the account of the person who connected it. If that person is a director with access to every client, the agent quietly has the same reach. Nobody intended that, and nobody notices until a draft for one client mentions another client's product.

So the first rule for agents in an agency is the same one that applies to freelancers you bring in for a single project: they see the folder for the job, and that's all.


Start with one space per client

Give every client a space of their own and keep everything for that client inside it. A layout like this works for most retainers:

Northfield Dental/
  AGENTS.md
  brief/
  brand/
  deliverables/
  feedback/
  meetings/
  NEXT.md
Northfield Dental/
  AGENTS.md
  brief/
  brand/
  deliverables/
  feedback/
  meetings/
  NEXT.md
Northfield Dental/
  AGENTS.md
  brief/
  brand/
  deliverables/
  feedback/
  meetings/
  NEXT.md

The brief and brand guidelines sit at the top, finished work goes in deliverables/, client comments in feedback/, and call recordings and their transcripts in meetings/. How to organize files across multiple clients goes into naming and structure in more detail, and Fabric for client work shows the wider setup.

The same spaces control which people see which clients. Fabric sets viewer, commenter, editor and admin roles at space and file level, so a junior designer on two accounts can be given those two spaces and no others. How to limit team members to specific client folders walks through it. Once the people are scoped this way, scoping the agents follows the same lines.


One agent per client in Agent Vault

Agent Vault lets you invite external agents, such as Claude, into your workspace as non-human team members. For an agency, the useful pattern is to treat each client's agent as a separate member with access to one space.

Say Northfield Dental's agent drafts social posts, summarizes calls and keeps the content calendar current. You give it access to the Northfield space, then choose its capabilities. Reading files, running searches and creating documents cover that work. Moving content and deleting items can stay off. For a retainer you might leave access in place indefinitely. For a three-week rebrand sprint, a week at a time keeps it tidy, and expired access ends on its own. Why AI agent access should expire explains the reasoning.

Sometimes an agent needs something outside its space, such as the agency's shared post templates. It sends a request and waits. You can approve it once, for a set period, indefinitely, or deny it. For folders that should never be opened casually, such as contracts and rate cards, you can require that access is always requested, so no agent reaches them on standing permission.

Every action an agent takes is logged with a timestamp: what it read, created, changed or deleted. You can filter the log by agent, by area, by period or by action. When a client asks which of their files your AI tools touched last month, you can filter by their space and show them. Fabric can also notify you when an agent's activity follows an unusual pattern.

Agent Vault is on the Pro and Team plans, and organization-wide policies are available on Team. It's a useful control for keeping clients apart. Whether your setup meets a particular client's contract or data protection terms is a question for your own legal and security review.


Give each client its own instructions

That AGENTS.md file at the top of each client space is where the client's rules live: tone of voice, words the client never uses, who signs off on what, which competitors not to mention. Codex reads AGENTS.md, and Claude Code reads CLAUDE.md, so some teams keep both. Either way, every agent working on that client reads it before starting, so the Northfield agent writes like Northfield and the bakery agent writes like the bakery.

Agents can't change these instruction files in Fabric, even when they have write access to the folder. That matters in agency work, where an agent reads a lot of material the client sends over. If a pasted brief contained text designed to redirect the agent, it still couldn't rewrite the standing instructions for the account. Changing them stays a job for the account lead. Your agent instruction files are a security risk covers why this matters.


Several people, several agents, one client

On a busy account, the copywriter's agent and the strategist's agent may both edit the same campaign plan in an afternoon. If one saves a change based on an older version of the file, Fabric refuses that write, and the agent re-reads the plan and reapplies its change. Neither edit is lost and no duplicate copy appears in the folder. When two AI agents edit the same file shows this step by step.

Client work also runs through email and chat. Agent Passes apply the same per-action controls to apps connected to Fabric, such as Gmail or Slack. An agent can be allowed to read a client thread and draft a reply without being able to send it, so a person still presses send on anything that reaches the client.


Handoffs inside the agency

Account work changes hands often: holidays, sick days, a new hire taking over a client. The handoff usually lives in someone's head. With agents in the picture, it helps to make it a file.

At the end of each working session, ask the agent to update NEXT.md in the client space with what's half done, what's waiting on the client and anything it was unsure about. When a colleague picks up the account on Monday, their agent opens that note and the recent files in meetings/ and feedback/ and carries on from there. It doesn't matter if the colleague uses ChatGPT and the original account manager used Claude, because both agents read the same folder. How to hand off work between AI agents has more on the pattern.


Handing the work to the client

At the end of a project, or at each milestone, the client needs their files. Because everything for the client is already in one space, you can share that space with them and they see only that space. How to give a client access to only their files covers the steps. If they're commenters, they can leave timestamped notes on video, draw on images and highlight text, and you can mark each comment completed as it's handled.

For a final delivery, you can publish the deliverables/ folder as a web page instead, with downloads allowed and, on Pro or Team, a password. What makes a client handoff impressive has ideas for the delivery itself.

When the engagement ends, revoke the client's agent from Agent Vault. Revocation is immediate, and it doesn't affect the agents you run for other clients.


What it costs

Fabric prices per person, so a client agent doesn't need a seat of its own. Running twelve client agents doesn't add twelve seats to the bill. See pricing for teams and should AI agents need a seat?

For the broader case for keeping agents' work in shared files, start with your AI agents need a shared drive, not a group chat, or read what a shared drive for AI agents is if the idea is new.


Frequently asked questions

How do I stop an AI agent seeing other clients' files?

Give each client their own space and give the agent access to that one space in Agent Vault. It can't read or search anything outside it unless you approve a request.

Can I use one AI agent for all my clients?

You can, but it means that agent can reach every client's files. A separate agent per client, each scoped to one space, keeps work for different clients apart.

Can a client see what our AI agents did with their files?

Agent Vault logs every agent action with a timestamp. You can filter the log by area to see everything agents did in one client's space and share that with the client.

Can an agent send emails to clients on its own?

Only if you allow it. With Agent Passes you can let an agent read and draft email without permission to send.

How do I hand a client account to a colleague who uses a different AI tool?

Keep a NEXT.md handoff note in the client's space. Their agent reads the same files whether it's Claude, ChatGPT or Codex, so nothing has to be exported.

How do I give a client access to only their own files?

Create a space for that client and share it with them. They see only that space.

What happens to the agent's access when a project ends?

Access you set for a fixed period ends on its own. You can also revoke an agent at any time and the change takes effect immediately.

Do client agents count as extra seats?

No. Fabric prices per person, so agents don't need their own seats.


Related pages


The workspace that thinks with you.

Ready when you are.

The workspace that thinks with you.

Ready when you are.

The workspace that thinks with you.

Ready when you are.