Best Ethical Wall Software for Law Firms: 6 Options in 2027

Key Takeaways

• Make the category decision first: choose the wall that lives in the system where your matters, files or billing already sit, because a wall beside those systems leaves gaps.

• Of the six products below, CosmoLex is the only one whose pricing page we opened shows per-user prices, at $49, $99 and $129 per user per month.

• Intapp Walls, iManage Security Policy Manager, NetDocuments and Fulcrum SCREENS publish no price on the pages we opened, so each needs a written quote.

• Microsoft Purview Information Barriers restricts two-way communication in Teams, SharePoint and OneDrive, and its documentation says it cannot restrict email.

• A workflow layer can route conflict hits, lateral hires and wall changes to a human reviewer, but it cannot replace the access controls inside your document or practice system.

• Before you sign, ask each finalist to show a restricted user's view of one real matter, including files and reports. None of the public pages we opened shows that view.

Short answer: match the wall to where your files live

An ethical wall is a documented information barrier that keeps a screened lawyer or staff member away from a matter's files, messages and billing.

TL;DR: Pick the wall inside the system that already holds your matters, get a written quote and a restricted-user demo from each finalist, and drop any tool that cannot show what a screened person sees.

Three categories cover most small-firm choices. Practice-management walls, like the one CosmoLex documents, hide the matter itself from restricted users, including its contacts, time and expense entries, invoices, tasks, notes and files, and they block a restricted user from running a conflict check on that matter. Document-management walls, like iManage Security Policy Manager and NetDocuments, control who can open a file wherever it is stored, which matters most when the document is where the exposure sits. Platform walls, like Microsoft Purview Information Barriers, restrict collaboration inside Microsoft 365. Intapp Walls and Fulcrum SCREENS sit above several systems and focus on managing the screens themselves.

Microsoft Learn's Information Barriers documentation shows the platform approach at work in 9 example scenarios. One of those examples bars a lawyer's data from one client from being accessed by a lawyer at the same firm who represents a different client, which is the core ethical-wall problem in a single sentence.

Glossary for this buying decision

• Ethical wall: a written, enforced barrier that keeps a screened lawyer or staff member away from a matter.

• Conflict check: a search of clients, matters and adverse parties before a new matter opens.

• Imputation: the rule that one lawyer's conflict is attributed to everyone at the firm. California's version lets a properly built screen prevent that in limited cases, according to San Francisco Bar Association (2018), which lists 3 conditions for screening a lateral lawyer.

• Lateral hire: a lawyer who joins from another firm and may bring a former-client conflict.

• Two-way restriction: a block on communication in both directions between two groups. Microsoft states that Information Barriers supports only this type.

• Mail flow rule: an Exchange rule that controls how email is routed. Microsoft points to these for email controls because Information Barriers does not cover email.

How we evaluated these tools

We judged six products against six weighted criteria. The weights are our judgment about what a small firm must verify before it signs. They are not a vendor rating, and we did not assign numeric scores because the public pages do not report comparable data.

We opened each product's own pages for features, pricing and any help article. For the legal rules, we used two independent sources: a San Francisco Bar Association summary of California's screening rule and an Oregon Professional Liability Fund post on screens. We left out products whose ethical-wall documentation we could not open. That includes Litera, where our searches returned nothing relevant; Thomson Reuters Elite, where we found only older material and no current feature page; and Clio and Rocket Matter, where the ethical-wall documentation was not reachable from the pages we could open.

What the public pages state, product by product

This matrix records what each vendor's page says. "Not stated" means the page we opened did not say so, which is not proof that the feature is missing. Read the table as a list of documented claims, not a ranking.

Oregon's Professional Liability Fund lists 4 places where case information sits, and it says each one needs its own safeguard, according to Oregon PLF (2024). The four are email, paper files, electronic documents and practice management software. A product that covers only one of those four places is a partial control, and the table above shows where each vendor's public claims stop.

Pricing and cost math

Pricing checked October 19, 2026.

Launch plan on CosmoLex: $49 per user per month according to CosmoLex (2026). The Core plan on CosmoLex costs $99 per user per month, and the Pro plan on CosmoLex costs $129 per user per month, as shown on the same page. The page offers a monthly and yearly toggle but does not show the yearly per-user price, so we do not convert these figures into annual quotes.

The seat math below multiplies each displayed CosmoLex per-user price by the seat count. These are arithmetic results, not quotes, and they assume the displayed rate applies to every seat.

Take a 10-lawyer firm with three walled matters and one lateral hire who brings a former-client conflict. If the firm moved its matters into CosmoLex and used the Core price cited above, the seat cost would be 10 × $99 = $990 a month, or $990 × 12 = $11,880 over a year, if the displayed rate held for the full year. The firm's admin would set the restriction matter by matter in CosmoLex's settings. If the firm instead stayed on Microsoft 365, Microsoft's pages we opened did not give a per-user figure for Information Barriers.

Vendor profiles

Each profile separates published facts from our read. Where a page did not state something, we say so.

Intapp Walls

Published facts: Intapp describes Walls as a way to "Set up, monitor, enforce, and report on ethical walls," and names SharePoint and Microsoft Teams as systems where its security extensions apply. Its page shows 2 consulting firms as users, FTI Consulting and AlixPartners, according to Intapp. The page publishes no price.

Intapp says more than 70 of the Am Law 100 rely on Walls according to Intapp (2026). That is Intapp's own figure, not an independent count. The same post says Walls policies sync into Harvey's Assistant, Vault and Spaces tools, and that the integration is generally available as of July 23, 2026. Harvey enforces the synced policies without creating, changing or deleting them, and it blocks access when it cannot confirm a user's rights.

Our read: Intapp's public material is the most explicit of the six on AI enforcement. Its examples are large and consulting firms, so a small firm should ask for a reference of its own size. Best fit: firms that run several systems and expect AI tools to read those files. Limitations: no published price, and the public page does not describe audit exports in detail. Implementation: ask for the sync steps, the list of policies that import, and what Harvey does when access cannot be confirmed.

iManage Security Policy Manager

Published facts: iManage calls Security Policy Manager "a governance layer that runs on top of iManage Work." Its page says walls can be built at 4 levels, client, matter, department or firm, according to iManage. The page says policies "update themselves as matters open, teams change, and lateral hires arrive," that every policy event is logged, and that reports can be generated as PDF or Excel. The page lists no price and routes pricing questions to the vendor.

Our read: iManage is the natural choice for a firm already on iManage Work that wants walls inside its document system. Limitations: the product lives inside the iManage platform, so a firm that does not already use iManage Work is making a platform change, not adding a wall. The page does not state email coverage. Implementation: users must confirm they have read their policy obligations before access is granted, scheduled reviews keep barriers current, and the FAQ says policies can push to connected systems such as Teams and SharePoint.

NetDocuments ethical walls

Published facts: Authorized users create, edit and apply security policies to specific people and files. Restrictions can target a user, a document or a whole workspace, which the page describes as "granular access controls at the user, document, or workspace level," according to NetDocuments. Reports show who accessed which documents. The page lists no price and points readers to a sales contact.

Our read: NetDocuments fits firms whose documents already live there, and the reporting is a practical proof point for clients who ask who opened a file. Limitations: the ethical-walls page does not describe how walls apply inside Microsoft Teams or other integrations, even though the site links to those integrations. Red flag: if the wall must cover email, ask the vendor for that in writing before you start. Implementation: name one owner for policy creation and ask for a sample report export.

Microsoft Purview Information Barriers

Published facts: Information Barriers "restricts two-way communication and collaboration between groups and users in Microsoft Teams, SharePoint, and OneDrive," according to Microsoft Learn (2026). The documentation says IB policies "can't restrict communication and collaboration between groups and users in email messages," so email needs Exchange mail flow rules. Segments come from Microsoft Entra attributes such as Department, MemberOf and Company, along with ExtensionAttribute1 through ExtensionAttribute15, and the attributes reference says each user belongs to exactly one segment, according to Microsoft Learn (2026).

Our read: this is the right candidate for a firm already paying for Microsoft 365 that keeps matters in SharePoint and Teams and can handle email separately. Limitations: the documentation says one-way rules are not supported, so a rule where Marketing can reach Day Traders but not the reverse cannot be built. The page also warns that enabling Information Barriers in environments without configured address book policies "can result in the loss of Address List visibility between all users." Implementation: the segments are defined with PowerShell cmdlets such as New-OrganizationSegment, and the licensing decision belongs to your Microsoft agreement, since the pages we opened show no per-user price.

Worked example: suppose a firm on Microsoft 365 keeps a conflicted matter in one SharePoint site and wants only the matching segment to reach it. Microsoft's SharePoint documentation shows an administrator running Set-SPOSite against a site URL on the contoso.sharepoint.com host, such as https://contoso.sharepoint.com/sites/ResearchTeamSite, with the -AddInformationSegment parameter and a segment GUID, and it says adding a segment switches the site to Explicit mode. A site can take up to 100 compatible segments, an organization can define up to 5,000 segments (250 in Legacy mode), and Microsoft says to wait 24 hours after activating policies for changes to propagate, with about 1 hour more after SharePoint Information Barriers is first enabled. Microsoft's audit log reference lists SiteIBSegmentsSet as the operation recorded when a segment is applied to a site, which gives the firm a dated record of the change. That covers files in the site, not email, so the firm still needs a mail flow rule for the same matter.

Fulcrum SCREENS

Published facts: SCREENS is a software-as-a-service case management tool added to Fulcrum GT's Upfront intake platform. It creates and manages ethical screens, sends notifications to people under a screen, monitors whether screens are still needed, and gives users and administrators a dashboard. The page says "Every action taken within SCREENS is fully auditable." It lists no price and points readers to the vendor for details. The announcement is at Fulcrum GT's SCREENS announcement.

Our read: SCREENS fits firms that want intake, conflicts and screen notices in one tool, especially if Upfront is already in use. Limitations: the public material does not name document systems, and the main SCREENS product URL we tried returned a not-found page, so confirm the current product name in writing. Implementation: ask which downstream systems the tool enforces screens in, and ask for the audit export before you buy.

CosmoLex ethical wall

Published facts: To configure walls, an admin needs the "Ethical Wall Admin" permission on the user record. The admin then opens a matter's settings under Matters, Edit, Settings, Ethical Wall, chooses Custom and moves the users to restrict into the Restricted list. Restricted users cannot view or filter the matter or its linked client, and they cannot see time and expense cards, invoices, tasks, notes, events, tagged emails, related transactions, bills or files. They also cannot run a conflict check against the matter, and reports show a "Secured Client" label in place of the restricted client name, according to CosmoLex Support.

Our read: CosmoLex is the only product here where the wall, the matter, the billing and the conflict check live in one system, which removes the seams that come from separate tools. Limitations: neither the support article nor the pricing page says which plan includes the ethical wall, so ask before you buy. Switching matter and billing into CosmoLex is a much larger project than adding a wall to an existing system. Implementation: one admin with the Ethical Wall Admin permission can set walls matter by matter.

Who this is for

A firm that already runs matters and billing in CosmoLex should price the wall inside that system first. A firm that keeps its files in iManage Work or NetDocuments should evaluate the document-system wall, because the file is where the exposure sits. A Microsoft 365 firm that can handle email separately can evaluate Information Barriers for Teams, SharePoint and OneDrive. A firm that wants intake and screen notices in one place, and already uses or is considering Upfront, should look at Fulcrum SCREENS. A firm running several systems that expects AI tools to read its files should put Intapp Walls on the shortlist.

Red flags: you need email covered and the only control you plan to use is Information Barriers; nobody in the firm will own wall changes and their approvals; or the vendor will discuss price only after a demo.

Where the wall stops and the workflow starts

A wall stops access, but it does not decide who should be screened or record that a decision was made. US Tech Automations can be configured for that gap as a proposed workflow, which would run as follows. The trigger is a new matter or a conflict-check hit in your practice system. The action compares the client and adverse-party names against a read-only export of the current wall list. The output is a review item for conflicts counsel and a draft notice to the responsible partner. No permission changes automatically. Human review points are counsel's approval of every proposed wall and a named partner's check of the draft notice. Prerequisites are read access or a scheduled export of the wall list and the matter intake fields from the practice system. None of the vendor pages we opened documents an export of wall lists, so confirm that with the vendor before designing the trigger.

A second proposed workflow handles lateral hires. The trigger is a new lateral record in your HR or roster system. The action pulls that lawyer's prior matter list from an export and flags any client that overlaps with an open matter. The output is a checklist for counsel covering the screen steps your state requires. California's version allows a lateral to be screened only when three conditions are met: the lateral did not substantially participate in the matter, is timely screened and receives no part of the fee, and written notice goes promptly to the former client. The ABA model rule differs in some respects, so check your own state's version. Counsel signs off on the screen, not the workflow.

Build it yourself or buy a wall?

The realistic alternative for many firms is stitching this together in Zapier, Make or n8n, or building it in-house. Those tools can keep run histories, retries and error branches, and they can produce audit evidence when configured properly. The buyer still has to design and own observability, meaning who sees a failed run, idempotency so a notice is not sent twice, escalation paths, access controls on the automation account, and maintenance when a field name changes in the practice system. A proposed design from US Tech Automations would configure the same run history, retry and error branch, approval step and audit log, with the export access, a named approver and a retention period you choose as prerequisites. Either way, the wall stays inside the document or practice system, because a workflow that sends notices cannot block a file from opening.

When a simpler option wins

When NOT to use US Tech Automations: skip a proposed workflow if your practice system's own wall already covers the matters you care about, because configuring that wall is simpler than adding a layer. Skip it if lateral hires and conflict hits are rare enough that a written checklist and the document-system wall cover them. Skip it if what you need is enforced access, since the proposed design routes approvals and logs decisions but does not change permissions in your document system. If you are choosing general drafting software rather than a wall, the drafting-tool comparison covers a different decision, and the guides for agencies and SaaS teams cover narrower versions of it.

Checklist before you request quotes

• Name the system that holds your matters, files, email and billing, and mark the one that carries the most risk.

• Ask each finalist for a restricted user's view of one real matter, in writing, including files and reports.

• Ask whether the wall covers email, chat and reports, and what it does not cover.

• Confirm which plan includes the wall, the price per user, the billing basis and any minimum seat count.

• Request a sample audit export and check that it shows who opened what.

• Name the admin who approves wall changes and set a review date for each active screen.

• Run the exception review on a schedule.

Frequently asked questions

Is an ethical wall the same as a conflict check?

No. A conflict check searches for potential conflicts before a matter opens, while an ethical wall restricts access once a conflict or lateral screen is in play.

Can Microsoft 365 alone give a small firm ethical walls?

Partly. Information Barriers restricts collaboration in Teams, SharePoint and OneDrive, but its documentation says it cannot restrict email, so you need mail flow rules or another control for email.

Do these tools publish prices?

Only one of the six does on the pages we opened: CosmoLex publishes per-user prices on its pricing page. The others are Quote-based, and the Microsoft pages we opened do not show an Information Barriers price.

Do walls stop AI tools from reading restricted files?

Only if the AI product reads the wall policy. Intapp says Harvey enforces synced Walls policies in its Assistant, Vault and Spaces tools, and iManage says its AI tools retrieve only content a user already has rights to see.

Is a workflow tool a substitute for a wall?

No. A workflow can route a conflict hit or a lateral hire to a reviewer and keep a log, but the access block has to live in the document or practice system.

What should a small firm ask for first?

Ask for a written quote, a restricted-user demo on one real matter that includes files and reports, and a sample audit export. Those three items show more than any feature list.

Next steps for a short list

Start with the system that already holds your matters and files, get written quotes and a restricted-user view before you sign, and treat any product that cannot show that view as unproven. A proposed review workflow for conflict hits and lateral hires would sit around the wall, not in place of it, as outlined in the US Tech Automations approach.