CMS Integration Writing Data Back to Case Management System in Eve

Last updated: March 10, 2026

Overview

This article resolves concerns about whether Eve modifies or writes data back to your case management system during integration. This concern typically arises when firms are evaluating integration security or have experienced data modification issues with other tools. Understanding Eve's read-only architecture ensures you maintain complete control over your case management system as the single source of truth.

Before You Start — Diagnosis

Confirm the following before reviewing the information below:

  • You have an active CMS integration configured in Eve

  • You are concerned about whether Eve can modify data in your case management system

  • You want to understand the data flow direction between Eve and your CMS

Fixes

Possible Cause: Misunderstanding of Eve's Integration Architecture

Cause: Users may assume that because Eve pulls data from the CMS, it can also push changes back to the CMS. This is a common concern when evaluating integration security and data integrity, especially if previous tools modified CMS data unexpectedly.

Steps: No action is required. Eve integrations are read-only by default. This means:

  1. Eve pulls data from your case management system (matters, documents, case information)

  2. Eve processes and analyzes this data within its own platform

  3. Eve never writes, modifies, or deletes data in your case management system

  4. Your CMS remains the single source of truth for all case information

  5. Any work performed in Eve (summaries, chronologies, demand letters) exists only in Eve unless you manually export and upload it to your CMS

Expected Outcome: You can confidently use Eve's CMS integration knowing that your case management system data remains completely protected from any modifications by Eve. All changes to case data must be made directly in your CMS through your normal workflows.

Possible Cause: Concern About Data Integrity During Sync

Cause: Firms may worry that the nightly automatic sync or manual sync operations could inadvertently trigger changes to CMS records, especially if the integration requires API write permissions during setup.

Steps: No action is required. The sync process is strictly unidirectional:

  1. During nightly automatic syncs, Eve only reads new or updated data from your CMS

  2. During manual syncs initiated from a matter in Eve, the platform only pulls in the latest documents and case information

  3. No sync operation—automatic or manual—can write data back to your CMS

  4. API credentials used for the integration are configured for read-only access

  5. Even if your CMS API technically allows write operations, Eve's integration is architected to never perform write actions

Expected Outcome: All sync operations complete successfully without any modifications to your CMS. Case information flows into Eve for AI-powered analysis while your CMS data remains unchanged and under your complete control.