What a wall is for
An ethical wall, sometimes called a screen, keeps information about one matter away from people at the firm who shouldn't have it. The classic case is a lateral hire. A lawyer joins from another firm, and on their old desk sat a file for the party your firm is now suing. The wall says that lawyer stays away from your matter, and the people working your matter don't go asking them about it.
Walls show up in other places too. A firm represents a client in a deal and a different client in a dispute that brushes up against it. A staff member has a family connection to a party. A matter is sensitive enough that the partner wants it limited to the people actually working it. Bar ethics guidance has a good deal to say about when a screen is appropriate and what it has to include. Whether one is needed on a given matter is a judgment for the lawyers, and that part never moves into software.
What software can do is make the wall real once someone decides it exists.
The gap between the memo and the system
At a lot of small firms, the wall lives in a memo and in people's good intentions. Meanwhile the document system lets anyone with a login open any folder. The billing system shows every matter to everyone. A shared drive has a folder called "Smith v. Jones" that the walled lawyer could click on by accident while looking for something else.
Nobody has to be acting in bad faith for that to go wrong. Search results are the usual culprit. You type a name into the firm's search bar and it returns documents from every matter where that name appears, including the one you're supposed to be walled off from. You didn't go looking. The system brought it to you anyway.
So the real question for any piece of firm software is simple: if a person is on the wrong side of a wall, can the system show them the file? If the answer is yes, the wall depends entirely on everyone remembering it, every day.
Matter-level access control, in plain terms
Matter-level access control means the software organizes everything by matter, and every matter has a list of who may see it. Your login carries your identity. Before the system shows you a document, a search hit, a summary, or a draft, it checks whether you're on that matter's list. If you aren't, the item simply doesn't appear on your screen, not even as a locked placeholder with the matter name showing.
A wall is the same mechanism pointed the other way. Instead of a list of who's allowed in, it's a named block: this person, kept out of this matter, regardless of any broader permission they'd otherwise have. A good system lets the block win. If a partner can normally see every litigation file but is walled off from one, the wall beats the partner role.
A few things separate a real implementation from a checkbox:
- It covers every path in. Browsing, search, exports, notifications, and anything a tool generates. A wall that blocks the folder view but leaks through search isn't doing its job.
- The firm administers it. Whoever handles conflicts at your firm should be able to set or lift a wall themselves, without filing a ticket with a vendor.
- It leaves a record. When the wall went up, who put it there, who it covers, and any attempt to reach the blocked matter. If anyone later asks whether the screen held, you want to be able to show it rather than just say it.
We've written before about what a tamper-evident audit trail is. Walls are one of the places where that record earns its keep.
Where AI tools punch holes
This is where it gets interesting for anyone thinking about AI. Many tools work by gathering up everything they can reach, building an index, and answering questions from that pile. If the pile includes every matter at the firm, a question asked by a walled person can come back with an answer shaped by the walled file. The tool doesn't have to quote the document for that to be a problem. A summary, a suggested fact, or a sentence in a draft can carry information across the wall without anyone noticing.
Firm-wide chat assistants raise the same issue. If the assistant can see everything and anyone can ask it anything, the wall is only as strong as the assistant's discretion, and software doesn't have discretion.
The safer design checks access before the AI ever reads anything. When you ask a question inside a matter, the system works only from documents in that matter, and only if you're allowed to be there. The answer can't draw on a file you couldn't have opened yourself, because the file was never in the room.
That's how we approached it in the Tiber River Legal Workbench. Matters are the unit of everything, walls are set by the firm, the review aids only draw from the matter in front of you, and the access record sits on hardware the firm controls. The attorney decides everything, including who sits on which side of a wall.
Questions to ask about any tool
You don't need to read code to test this. Ask the vendor to set up a wall during the demo, then log in as the walled person and search for a name from the blocked matter. Ask what happens when someone tries to reach a matter they're walled off from, and where that attempt gets recorded. Ask whether the AI features use the same permission check as the document browser or a separate one. And ask who at your firm can put up a wall on a Friday afternoon, when the lateral starts Monday.
If the answers are vague, the wall at your firm still lives in a memo.
Tell us how walls work at your firm today
The Tiber River Legal Workbench is a matter intelligence appliance for litigation and personal injury practices, running on hardware your firm owns. Whoever handles conflicts at your firm knows where screens get tricky better than any vendor does. We're inviting a small number of Maryland firms to shape it as design partners.
Start the conversationOr write to josh@tiberriverconsulting.com