A departing employee can lose access to the firm’s email and case-management system within minutes, yet still retain a valid session, a local download, or access to an AI workspace that contains medical records and demand drafts. In a plaintiff personal-injury practice, that gap is not merely an IT inconvenience. It can expose protected health information, attorney work product, negotiation strategy, and client communications after the person’s role has ended.
This article gives PI firms a practical offboarding and matter-reassignment framework for AI-processed case files: identify every access path, revoke credentials in the right order, preserve the case record, and verify that the new matter team can continue the work without relying on the former user’s account.
Why ordinary offboarding misses legal-AI access
Most firms have a familiar departure checklist: collect the laptop, disable Microsoft 365 or Google Workspace, remove the employee from the case-management platform, and redirect email. The problem is that an AI-assisted demand workflow may add several less-visible access paths. A staff member may have a direct vendor login, single sign-on through the firm identity provider, an active browser session, API credentials used by an integration, exported chronologies, downloaded source records, or shared links that remain usable after the primary account is disabled.
Matter reassignment creates a second operational risk. If an employee organized records, added issue notes, or reviewed draft language inside a personal workspace, the firm may revoke access successfully but strand important work. The replacement attorney or case manager then has to reconstruct what was uploaded, which sources supported the draft, what was verified, and what remained unresolved. Security and continuity have to be handled together.
The legal duties do not disappear because the system is new. California Rule of Professional Conduct 1.6 requires lawyers to protect confidential client information, while Business and Professions Code section 6068(e)(1) imposes a duty to maintain client confidences. For workflows involving electronic protected health information, the HIPAA Security Rule’s workforce-security provisions address termination procedures under 45 C.F.R. § 164.308(a)(3)(ii)(C), and its access-control standard appears at 45 C.F.R. § 164.312(a)(1). Whether a particular firm is acting as a covered entity or business associate depends on the arrangement, but the operational lesson is broader: access should follow current job responsibility, not historical convenience.
Map the full access chain before revoking accounts
A useful offboarding process begins with an access map, not a list of devices. For each AI-supported matter workflow, the firm should know how a user authenticates, where source files are stored, whether files can be exported, and which integrations act independently of that user.
Identity and session access
Determine whether the user signs in through single sign-on, a vendor-specific account, or both. Disabling a central identity account may not terminate a separate password login. It may also leave browser sessions or refresh tokens active until the vendor expires or revokes them. The firm should be able to answer four questions for each system:
- Can an administrator suspend the user immediately?
- Does suspension terminate active sessions on every device?
- Can the user create API keys, public links, or personal access tokens?
- Does the audit log record the suspension, session termination, downloads, and later access attempts?
If the answers are unclear, the issue belongs in vendor due diligence before the next departure occurs. A policy that says “disable access” is incomplete when nobody knows which action actually invalidates a live session.
Files, exports, and derivative work
The source record and the AI-generated output may exist in different places. Medical records may remain in the case-management system, while a chronology export sits in cloud storage and a demand draft is attached to an internal message. Build an inventory that covers source records, extracted text, summaries, chronologies, prompts, draft versions, review notes, and final exports.
That inventory should distinguish the firm’s authoritative matter record from temporary working copies. The firm does not need to preserve every disposable duplicate, but it should retain enough to explain what evidence was used, what the tool produced, what a human changed, and which version was approved. That is especially important when a reassigned matter is approaching a demand deadline or when treatment records continue arriving after the original draft was created.
Shared credentials and integration accounts
Shared logins make offboarding slower and less reliable because the firm cannot revoke one person without changing access for everyone. They also weaken auditability: a log entry tied to “Demand Team” does not identify who viewed or exported a file. Each staff member should have an individual account, while integrations should use separate service credentials with narrow permissions.
When a departing employee knew a shared secret, rotate it even if the employee says it was never saved. Review API keys, automation connectors, browser extensions, password-manager collections, shared mailboxes, and cloud folders. A token used by an integration may continue retrieving case data after the human user’s account is gone.
A five-stage offboarding and reassignment procedure
The safest process assigns an owner and a time for each action. “HR notified IT” is not the same as confirming that a legal-AI account was disabled and its sessions were terminated.
- Set the effective cutoff. HR, the supervising attorney, and the system administrator should agree on the exact time access ends. For an involuntary departure or a role involving broad medical-record access, prepare the revocation steps before the separation meeting.
- Capture matter state without preserving unnecessary access. Before disabling the account, transfer ownership of active matters, shared workspaces, draft demands, source lists, and review notes to a firm-controlled administrator or successor. Do not ask the departing user to keep access temporarily “in case questions come up.”
- Revoke every identity path. Disable the identity-provider account, suspend the direct vendor account, terminate active sessions, revoke personal tokens, remove group memberships, rotate known shared secrets, and disconnect personal devices. Record who completed each action and when.
- Verify the authoritative record. The supervising attorney or reassigned case owner should confirm that the matter contains the current medical records, treatment chronology, billing information, liability materials, draft history, and unresolved issue list. AI output should be treated as a draft work product that still requires attorney review for accuracy, completeness, and strategic judgment.
- Test from both sides. Confirm that the former user can no longer authenticate or reach shared links, and confirm that the successor can access the materials needed for the matter. Review audit logs for unusual downloads or access immediately before departure, applying the firm’s written policy rather than improvising an investigation.
For planned departures, firms can complete the transfer review one or two business days before the cutoff while keeping final revocation tied to the effective time. For immediate departures, security takes priority; administrators can preserve firm-owned workspace content after access is suspended.
Controls that make the next departure routine
Offboarding should be designed into the workflow rather than rebuilt for each employee. A practical control set includes:
- Role-based access: Staff should see only the matters and functions required for their current assignments.
- Firm-controlled ownership: Case workspaces, prompts used in production, and exports should belong to the firm, not a user’s personal account.
- Central authentication: Single sign-on and multifactor authentication reduce credential sprawl, provided direct fallback accounts are also governed.
- Session and token revocation: Administrators need a documented way to invalidate live sessions, API keys, and shared links.
- Export rules: Define where downloaded records and drafts may be stored, how long temporary copies remain, and how deletion is confirmed.
- Audit review: Preserve logs long enough to reconstruct access, uploads, downloads, sharing, and administrative changes around a reassignment.
- Quarterly access certification: Matter owners should confirm that team membership still matches active responsibility instead of waiting for an annual review.
These controls also reduce everyday overexposure. A paralegal moved from one litigation team to another should not retain indefinite access to every prior matter merely because no one closed the permission loop.
How Legal Power AI fits
Legal Power AI is built for plaintiff PI demand workflows, but the firm remains responsible for user administration, source accuracy, and attorney review before any document is sent. Firms evaluating the platform’s privacy and data-handling posture can review the Legal Power AI FAQs. The platform processes data with BAAs from OpenAI and Anthropic, which are HIPAA-eligible vendors, while attorneys must still apply their own access, retention, and supervision policies to each matter.
Make access revocation part of matter management
A clean departure is not complete when the laptop is returned. It is complete when the former user’s sessions, tokens, shared links, and direct accounts are disabled; the firm’s authoritative record is intact; and the successor can identify the sources, drafts, and open issues without depending on a personal workspace.
The same discipline belongs upstream. As discussed in Privilege-Aware Prompting: What Plaintiff Firms Should Avoid Putting Into Generic AI Tools, confidentiality depends on workflow choices as much as tool selection. Build access ownership and reassignment into the AI process before the next staffing change, and offboarding becomes a controlled administrative event instead of a scramble around sensitive PI files.
See a PI-specific demand workflow built around attorney review. Discover Legal Power AI in action →