Clio Manage Integration

Exit Protocol for Clio Manage

Select in Clio. Review locally.

Name: Exit Protocol
Author: Exit Protocol

Select a financial document from a Clio matter and stage extraction candidates in Exit Protocol. The current integration stops at explicit local review: it does not automatically import a ledger, create a claim, run LIBR, generate a workpaper, or upload a file to Clio.

Connect Clio View Demo Flow

Selected-document workflow

User-triggered

01 · OAuth Authorize scoped Clio access for the signed-in user.

02 · Select Choose one matter and one financial source document.

03 · Stage Create an owned local extraction-review job without importing candidates.

04 · Review Approve local candidates explicitly; no automatic Clio writeback occurs.

User-triggered only

No workspace sweep. Staging reads only the selected matter document; any workpaper upload requires separate reviewed finalization and user confirmation.

Configuration-dependent OAuth Connection requires operator-configured credentials, region, scopes, and an exact redirect URI.

Selected-document staging tested Automated tests cover OAuth boundaries, matter/document selection, local staging, ownership, and failure modes.

App Directory review materials in preparation No public App Directory listing, endorsement, partnership, or certification is claimed.

User-triggered workflow

One document path, with a review gate at every consequential step.

Exit Protocol does not sweep a workspace or silently process every file. The user chooses the matter, chooses the source document, and starts the sync.

Connect

Clio handles authorization. Exit Protocol encrypts the resulting access and refresh tokens at rest for the connected user.

Select

The cockpit lists accessible matters and identifies supported financial PDF, image, and UTF-8 CSV sources without altering them.

Stage candidates

The selected document is stored as source evidence and extraction candidates are staged in an owned local review job. No candidate is imported automatically.

Review locally

The user reviews and explicitly approves candidates in Exit Protocol. A separate source-confirmation action can run deterministic LIBR, save the local workpaper, and explicitly attempt to upload a new PDF to the selected matter.

Current explicit-review boundary The implemented path keeps extraction, ledger import, source confirmation, calculation, and optional workpaper upload as separate user actions.

1 user-selected source document

0 automatic ledger imports

0 automatic Clio uploads

Permission boundary

The integration asks for what the workflow actually uses.

Matter access locates the selected record. Document read access lists and downloads the selected source. Document-create access is used only when the staging user separately confirms finalization and explicitly attempts to upload the generated workpaper.

Matters: Read List accessible matters and load the selected matter's display metadata.

Documents: Read List matter documents and download only the financial document selected for analysis.

Document writeback After extraction approval, source review, deterministic calculation, and local report storage, a separate user-confirmed action creates a new PDF in the selected matter.

Not requested No billing, time entry, calendar, contact editing, matter editing, or source-document deletion workflow.

Exit Protocol does not edit, replace, or delete the source document. Staging creates local review records only; explicit finalization may add a separate generated workpaper to the selected matter.

Downstream local output

A workpaper is available only after separate local review and calculation steps.

After extraction approval, a user must separately establish source provenance, create a claim, run deterministic LIBR, and generate a workpaper in Exit Protocol. The staging action performs none of those steps automatically. Finalization is a separate user-confirmed action that stores the local report before attempting to upload a new PDF to the selected Clio matter.

Source identity

Clio matter reference, source filename, source document ID, and source SHA-256.

Ledger reconciliation

Opening balance, deposits, withdrawals, closing balance, and the computed difference.

Deterministic chronology

The transaction sequence, source candidate, selected assumptions, and LIBR result.

Version manifest

Ingest engine, calculation engine, report template, and calculation input snapshot references.

Output integrity

A SHA-256 hash for the final generated PDF and the supporting integrity manifest.

Review notes

Prominent assumptions and warnings for counsel or a qualified forensic reviewer.

Reviewer materials

Technical boundary documentation for App Directory and integration review.

The Clio workflow runs through the production dashboard and OAuth path. For API surface, permission boundaries, CSRF rules, and integrity verification, reviewers can use the public V1 reference without requesting separate credentials.

Technical reference for reviewers

Exit Protocol API V1 — documented, tested, session-based

Partner and App Directory reviewers can inspect the bounded V1 JSON surface at /api/ before any machine-to-machine credential program. V1 documents health checks, public file verification, and the authenticated single-claim LIBR workpaper workflow.

Authentication model Protected endpoints use authenticated dashboard session cookies — not external API keys in V1.

Case-party access boundary Access is based on case membership and permissions, not the dashboard active_case_id UI session.

Unsafe POST controls Calculate and export require CSRF tokens. Public verify is intentionally CSRF-exempt.

Integrity path Export metadata, download bytes, and /api/v1/verify/ use exact-byte SHA-256 matching.

V1 scope: single-claim LIBR workpaper export only. Multi-claim pro-rata workpapers require separate review. Report downloads require a live authenticated session and are not signed public URLs. Machine API keys (scopes, rotation, audit logs, partner onboarding, revocation) are a separate future project.

Open API V1 documentation Public file verification

Integration FAQ

The practical questions, answered plainly.

How does a firm install the integration?

A signed-in Exit Protocol user selects Connect Clio, reviews the Clio consent screen, and grants the requested matter and document permissions through OAuth 2.0.

Is document synchronization automatic?

No. The workflow is user-triggered. The user selects a matter, selects a financial document, and explicitly starts selected-document staging.

What happens if the extracted statement does not reconcile?

The extraction job remains local and cannot be approved as a reconciled ledger until the source rows are reviewed and the statement controls pass. No LIBR analysis or Clio upload runs.

What does Exit Protocol change inside Clio?

The current path does not change the selected Clio matter or document. It downloads the selected source and creates local evidence, account, and extraction-review records.

How is AI used in the legal calculation?

LIBR itself runs through deterministic code over a normalized transaction chronology. Potential source characterization and all legal conclusions remain review decisions.

Integration demo

See the exact OAuth and matter-sync path.

Open the demonstration gateway to connect Clio, select a matter, inspect the document inventory, and enter the integration cockpit.

Open Demo Flow

Clio is a trademark of Themis Solutions Inc. Exit Protocol is an independent third-party application. No public App Directory listing, endorsement, partnership, or certification is claimed. For full details on data handling, permissions, and user rights, see our Privacy Policy and Terms of Service.