Should privileged or work-product materials live in MiOpsAI?

No. Privileged communications, attorney work product, litigation strategy, substantive matter analysis, and any documents subject to the attorney-client privilege should stay inside your document management system, matter management platform, and secure client portal. MiOpsAI is not designed to be a privileged-materials repository and should not be used as one.

The scope of what belongs in MiOpsAI is the operational layer: client intake coordination, scheduling, non-substantive status updates, engagement letter routing, matter opening logistics, vendor coordination, marketing, business development, and internal team coordination. All of that is important, none of it is privileged in the technical sense.

When operational threads accidentally cross into privileged territory (a client sends confidential strategy detail through the intake channel, an internal message references litigation strategy), LizziAI is trained to redirect the thread into your matter management system or secure portal and to flag the crossover for the responsible attorney. The operational side sees that a redirect happened, not the content of what got redirected.

The practical reason for this discipline is twofold. First, keeping privileged materials in a system explicitly designed for them (with the retention rules, access controls, and audit trails your ethics and malpractice carriers expect) is cleaner than trying to retrofit an operational platform to hold them. Second, if a discovery dispute ever arises about the privilege status of a specific communication, having a bright line between "operational (MiOpsAI)" and "privileged (matter management)" makes the analysis clean instead of ambiguous.

MiOpsAI is per-tenant AES-256 encrypted and never crosses tenant boundaries, and every access is logged. Those controls are solid for operational data. They are not a substitute for the matter management platform your firm already uses for the substantive work. See the security and compliance FAQ set for the full boundary.