
Kurt FischmanFounder, Machine-like
Kurt is the CEO of Machine-like, the Managed Agent Operations platform.

Law firms connecting artificial intelligence to practice management software must enforce four architectural boundaries before granting access: read-only API scopes by default, user-level permission inheritance to protect ethical screens, verified zero-retention vendor terms, and human approval gates for every database write. Treating AI as an ordinary software plugin risks exposing privileged client communications across conflicting matters or permitting unverified models to alter firm records without attorney supervision.
Connecting an artificial intelligence tool to your firm's practice management software feels like a routine administrative choice. Modern legal software marketplaces make integration look like a single click. You browse an app directory in Clio, MyCase, or PracticePanther, select an AI productivity add-on, and click "Authorize." Within seconds, the tool promises to draft intake notes, summarize deposition transcripts, coordinate client follow-ups, and log billable tasks.
For a managing partner or practice manager running a growing firm, that promise sounds like immediate margin relief. Legal administrative overhead consumes hours of skilled staff time each week. Routine document sorting, calendar updates, and client status messages don't generate revenue, but they require precision. Delegating those repetitive coordination jobs to automated tools seems obvious.
Yet connecting an AI agent to your core database is fundamentally different from connecting an accounting sync or a digital signature tool. Traditional software integrations use predictable, deterministic code to transfer specific data fields between two systems. When you connect a calendar sync, it looks at calendar events and nothing else. It doesn't read confidential matter narratives, summarize settlement negotiations, or attempt to infer next steps on open litigation.
An AI tool operates across unstructured language. To draft a motion outline, extract intake facts, or summarize a client email, it must ingest broad bodies of text. If that connection isn't bounded by strict permission layers, you aren't simply adding software; you're introducing an uncredentialed actor into your firm's confidential files. That's why managing partners must establish clear technical and operational boundaries before authorizing any connection.
When a law firm evaluates a standard software integration, the diligence checklist is familiar. You check uptime statistics, confirm user license fees, and ensure the data sync doesn't create duplicate calendar entries. Software behaves like plumbing: water flows through designated pipes into designated basins.
AI tools don't behave like plumbing. They behave like nonlawyer staff members who possess extraordinary reading speed but zero innate professional judgment. Under American Bar Association Model Rules 5.1 and 5.3, partners with managerial authority must establish reasonable measures ensuring that nonlawyer assistants and outside contractors comply with the professional obligations of the firm.1 When you grant an automated model access to your practice environment, that supervisory obligation doesn't vanish.
The central misunderstanding in many small law practices is assuming that an integration approved in a marketplace is pre-configured for legal ethics. Marketplaces verify technical interoperability, not regulatory compliance. Most standard integrations request broad application-level permissions that allow the tool to read every matter, contact, document, and invoice across your entire database. For a general business, broad read access is convenient. For a law firm, it's an immediate ethical liability.
Practice management systems manage authorization through open authentication protocols, commonly known as OAuth scopes.2 When an application asks for permission to connect to your firm's database, it presents a bundle of requested scopes. These scopes govern what types of data the application can read, create, update, or delete.
The structural problem with standard OAuth scopes is that they operate at the account level rather than the matter level. In systems like the Clio Platform API, selecting read permissions for matters grants access to every matter record across the firm.2 If your firm represents a plaintiff in commercial litigation, and a lateral associate joined your firm with an ethical screen separating them from an adverse co-defendant, standard user permissions in your practice software may keep that associate out of the file.
However, if you connect a third-party AI assistant using an administrative token or a firm-wide service account, that tool can bypass those ethical walls completely. An AI agent asked to summarize firm litigation matters or cross-reference corporate disclosures will query the entire database unless specifically partitioned. If an agent digests records from a screened matter and generates a summary accessible to other attorneys, the firm has suffered an ethical breach. Modern document repositories like NetDocuments address this through protocols like the Model Context Protocol, which enforce user-scoped permissions and existing ethical barriers directly at the retrieval layer.3 Without that user-level mapping, an integration turns your confidential silos into a single shared pool.
Confidentiality under Model Rule 1.6 is broad and non-negotiable. It covers all information relating to the representation of a client, regardless of source.1 In ABA Formal Opinion 512, the Standing Committee on Ethics and Professional Responsibility made clear that lawyers cannot enter client confidences into external generative tools without understanding how that data is stored, processed, and protected.1
State bars have issued matching guidance. The State Bar of California requires lawyers to review vendor terms of use to verify that provider agreements strictly prohibit using client information for model training or sharing data with unauthorized third parties.4 The Florida Bar similarly held in Ethics Opinion 24-1 that attorneys must research a program's policies on data retention and self-learning before inputting client confidences.5
Before connecting any AI tool to your firm's systems, your written agreement with the vendor must satisfy four non-negotiable points:
First, the contract must guarantee zero model training. The vendor must explicitly contract that client data, prompts, and document text won't be used to train, tune, or improve foundation models.
Second, the terms must impose strict retention limits. Prompts and retrieved context must be wiped immediately following inference, with zero long-term caching in external server logs.
Third, the vendor must disclose all subprocessors. The agreement must identify all third-party cloud hosts, embedding providers, or model endpoints, with written notice required before adding new subprocessors.
Fourth, confidentiality and intellectual property ownership must remain absolute. All inputs and outputs must remain the exclusive property of the firm, protected by encryption in transit and at rest.
If a vendor relies on consumer terms of service or refuses to provide a commercial agreement that guarantees zero training on firm inputs, you cannot connect that tool to your practice management system.
Connecting an AI agent to legal software requires shifting from broad application permissions to restricted, auditable operations.
| Architectural Layer | Default Marketplace Integration | Governed Legal Connection | Governing Standard |
|---|---|---|---|
| API Access Scope | Firm-wide read and write permissions across all database records | Read-only access limited to specific endpoints and object classes | Clio Platform API Scope Rules 2 |
| Cross-Matter Isolation | Service tokens bypass internal matter restrictions and conflict walls | Inherits user-authenticated permissions and existing ethical screens | NetDocuments Model Context Protocol 3 |
| Vendor Data Handling | Prompts and documents may be stored or used to train models | Contractual zero-retention terms with no model training permitted | ABA Formal Opinion 512 1 |
| Database Modifications | Autonomous direct updates to custom fields, dates, or matter notes | Structured candidate proposals requiring attorney review and approval | California Practical Guidance on AI 4 |
| Operational Logging | Basic HTTP error logs or transient conversational histories | Immutable audit trails recording user, matter ID, timestamp, and human sign-off | Florida Bar Ethics Opinion 24-1 5 |
A firm that isolates read permissions, enforces matter walls, and gates every database write can deploy automation without compromising its ethical obligations.
The table illustrates that commercial automation is possible only when boundaries are clear. Instead of granting blanket access, a firm establishes specific operational conduits. Administrative intake tools don't need access to billing ledgers. Document summarization tools don't need permission to delete files or file court notices. By isolating each tool to its designated job, the firm minimizes exposure while capturing the operational leverage of automated workflows.
The most dangerous permission you can grant an automated tool is unsupervised write access. An AI assistant that can read matter files is an analysis engine; an AI assistant that can write directly to your database is an autonomous actor.
Database writes in legal software have strict relational dependencies. In practice management platforms, changing a custom field, logging a communication, or updating a calendar date triggers downstream automations. If an AI tool attempts to update a picklist field with a hallucinated label or overwrites an attorney's handwritten interview notes, the data corruption can go unnoticed for weeks. Worse, an automated tool that autonomously sends an email to opposing counsel or submits a docket entry exposes the firm to severe professional liability.
The governing principle for legal AI operations is read-first, write-last. The integration must start strictly in read-only mode. The model reads the intake submission or correspondence, extracts key facts, and drafts a proposed update in a staging environment.
A licensed attorney or authorized staff member must review and approve that proposal before any change touches the live practice management database. The tool proposes; the professional decides. That human gate ensures that clerical accuracy and legal judgment remain firmly in human hands, satisfying the supervisory obligations mandated by professional conduct rules.1
When a question arises regarding how a particular entry appeared in a client file, oral explanations aren't sufficient. If a court, an insurer, or a client asks how a deadline was calculated or why a confidential document was accessed, the firm must produce documented evidence.
A compliant AI connection produces an append-only, tamper-evident audit log for every interaction. That log must record:
First, the timestamp of the query or action.
Second, the authenticated user or service account initiating the request.
Third, the matter identifier and specific object classes accessed.
Fourth, the exact tool invoked and parameters passed.
Fifth, the candidate text or structured proposal generated by the model.
Sixth, the identity of the attorney or staff member who reviewed and approved the change.
Crucially, integration logging must balance defensibility with data hygiene. While the log must record that a specific matter was accessed to generate an intake summary, it shouldn't dump complete, unencrypted deposition transcripts into plaintext developer error monitors. Logs must be stored securely, encrypted, and retained according to the firm's document retention schedules.
ABA Formal Opinion 512 doesn't ban generative AI in legal practice; rather, it establishes that existing ethical rules apply fully to automated tools.1 The opinion requires lawyers to understand tool capabilities, protect client confidentiality under Rule 1.6, verify that vendor terms prohibit data training, and supervise all AI work product before relying on it.1
AI integrations connected via account-level administrative tokens can see protected matters unless specifically restricted by user-level permissions.3 To prevent cross-matter data contamination, firms must ensure that API connections respect existing ethical walls and inherit the specific permissions of the authenticated user rather than using firm-wide service keys.3
Law firms shouldn't permit AI tools to write directly to practice databases without human review. Best practice requires a read-first architecture where the AI prepares a structured proposal and an attorney or designated staff member explicitly approves the change before it updates live matter records or client ledgers.1
Firms must refuse integrations with vendors that use client information to train models unless the affected client provides informed, written consent.1 Under guidance from the American Bar Association and state bars, inputting client confidences into self-learning models without explicit consent violates the duty of confidentiality under Model Rule 1.6.1 4
Your work should be about creativity, solving problems, and building relationships.
Leave the machine-like tasks to us.