Agentic FabriqRestrict agents to specific cases, clients, document sets, or jurisdictions.
Limits are set case by case, so an agent’s reach ends at the engagement it serves.
SOLUTIONS / Legal
Keep legal authority and sensitive information within clear boundaries
Control how agents access privileged information, create obligations, and act on the company’s behalf.
01 / IDENTITY02 / POLICY03 / AUDIT
01 / THE CONTEXTPrivilege has edges.
Privilege has edges.
So should the agent.
Legal agents may review contracts, conduct discovery, summarize communications, or negotiate standard terms. These workflows involve privileged material, confidential data, retention requirements, and actions that may create legal or commercial obligations.
Section 9 (Indemnity). The supplier shall indemnify the customer against , save for losses arising from .
legal-agent may propose edits inside the playbook. A nonstandard indemnity goes to counsel rather than being accepted.
Matter 24-118the engagement this agent serves — readable- Matter 24-092another client — out of reach entirely
Send to an external domainno send in this agent’s grant — an attorney’s act
02 / IN PRACTICE
Autonomy, with accountability.
ILLUSTRATIVE · ONE FLOOR, ONE ENGAGEMENTlegal-agent, acting for the counsel who owns the matter
MATTER 24-118 · OPENSupply agreement, Northwind
- Read the matter file and its history
- Draft a redline inside the playbook
- Read the correspondence on this matter
MATTER 24-092A different client
“Summarise every indemnity we have agreed” stops at the wall: these files are not in the engagement the agent serves.
Blocked · no door from 24-118MATTER 23-771Closed in March
The engagement ended and the room was shut with it, rather than the grant living on in somebody’s cleanup list.
Blocked · room shutTHE WAY OUTSend the response to opposing counsel
Anything that leaves the firm or creates an obligation waits at this door, addressed and ready, until a named attorney opens it.
Held · counsel turns the keyThe walls are not a habit of the agent’s: they are where the engagement ends. The same agent, asked the same question by counsel on 24-092, would be standing in a different room with different walls.
03 / WHAT CHANGES
Control, in the details.
Keep one client’s case files from leaking into another’s.
A broad question cannot pull in another client’s confidential files — those documents are simply out of reach.
Limit which terms an agent may propose, modify, or accept.
Playbook boundaries become policy: nonstandard terms route to counsel instead of being silently accepted.
Keep the authority to finalize out of the agent’s hands.
Accepting terms and executing an agreement are not actions the agent is granted, so the step that creates an obligation stays with an attorney.
Control external sharing and destination domains.
Sends are checked against approved recipients and domains, blocking a privileged document from reaching the wrong inbox.
Record the source material and the decision behind each action.
Work product carries its provenance — which documents informed it, which checks ran, and the attorney it was done for.
Revoke access when a case closes or an outside party’s engagement ends.
Access is tied to the engagement and ends with it, instead of living on in forgotten grants.
THREE LAYERS. ONE DECISION.
The boundary travels with the work.
Explore the context attached to every request.
What is this agent allowed to do?
legal-agent has a defined purpose and a bounded set of tools.
Whose authority travels with it?
The request acts for counsel, using that person’s permissions.
Where does the action land?
The policy applies to the requested action within Matter workspace, before the tool executes.
04 / WAYS TO PUT IT TO WORK
Built for your real workflows.
01A contract-review agent that can suggest edits but cannot accept nonstandard indemnification terms.
The agent proposes edits within the playbook; nonstandard indemnification terms are flagged to counsel, never accepted autonomously.
Identify→Authorize→Record
02An e-discovery agent limited to a defined legal hold and reviewer group.
Scope pins the agent to the hold’s document set and reviewer group, keeping collection defensible.
Identify→Authorize→Record
03A legal-intake agent that can classify requests but cannot expose privileged advice.
Classification runs on the request itself; privileged advice stays outside the agent’s readable scope entirely.
Identify→Authorize→Record
04An outside-counsel agent restricted to a single case workspace.
External counsel’s agent sees one case workspace, for the length of the engagement, and nothing else.
Identify→Authorize→Record
QUESTIONS
A closer look.
Does this require replacing our document management systems?+
No. Fabriq drops in between agents and the systems you already use. Case files stay where they are; Fabriq decides, per request, which documents an agent can reach and what it may do with them.
What happens when a case closes?+
Access tied to the case ends with it. Agents, outside counsel, and temporary staff lose their access automatically, and the case record keeps the full history of who and what touched it.
Can we keep the risky actions out of an agent’s hands?+
Yes — research and drafting are granted while executing an agreement or accepting terms is not, so those actions never appear in the agent’s tool list. Every call it does make is logged with the attorney it acted for.
Can access differ per attorney, case, and engagement?+
Yes — reach resolves from the person the agent works for. An associate’s agent sees that associate’s cases, a screened attorney’s agent inherits the screen, and outside counsel’s access is limited to one workspace and ends with the engagement.
What does the record show if work is challenged?+
Every agent action carries who asked, what was accessed, and the verdict — a defensible trail you can query per matter, per person, or per time window.
Where do system credentials live?+
In Fabriq’s vault, injected at call time — no passwords in prompts or configs on attorney laptops, and disconnecting a system cuts access immediately.