Home | Connectors | Consonance | Consonance - OpenText eDOCS Integration and Automation
Data flow: Consonance to OpenText eDOCS, with status updates back to Consonance
Publishing teams can send author agreements, licensing contracts, translation rights agreements, and vendor contracts from Consonance into OpenText eDOCS for legal review, redlining, version control, and approval. eDOCS provides the secure matter-centric repository legal teams need, while Consonance retains the publishing workflow context and final contract status. This reduces email-based document handling, improves auditability, and ensures editorial and rights teams always know which agreements are approved, pending, or rejected.
Data flow: Bi-directional
Consonance can push rights-related documents such as permissions letters, subsidiary rights agreements, and license confirmations into eDOCS for long-term legal retention. In return, eDOCS can provide the latest approved versions back to Consonance so rights managers work from a controlled source of truth. This supports faster rights clearance, reduces the risk of using outdated agreements, and gives legal teams a structured repository for publisher-specific matters.
Data flow: Consonance to OpenText eDOCS
When a title enters a legal review, dispute, or compliance-sensitive situation, Consonance can transfer manuscript drafts, editorial correspondence, and production files into eDOCS under the relevant matter. Legal teams gain secure access to the full document history, including version lineage and supporting evidence. This is especially valuable for defamation risk review, copyright disputes, and contractual claims where publishers need a defensible record of what was approved and when.
Data flow: OpenText eDOCS to Consonance
For documents that require strict legal control, such as indemnity clauses, contributor agreements, or settlement-related publishing correspondence, eDOCS can serve as the master system of record. Consonance can retrieve the approved version and attach it to the relevant title, project, or rights record. This ensures editorial and production teams do not work from drafts or superseded files, reducing rework and legal exposure.
Data flow: Consonance to OpenText eDOCS
If a title triggers a dispute, such as a copyright claim, breach of contract issue, or permissions challenge, Consonance can create or update a corresponding matter in eDOCS with the relevant title metadata, contract references, and document set. Legal teams can then manage the case in eDOCS while publishing teams continue tracking the title in Consonance. This creates a clean handoff between publishing operations and legal case management, improving response time and accountability.
Data flow: Consonance to OpenText eDOCS
Consonance can export publication milestones, manuscript approval records, metadata snapshots, and release dates into eDOCS to support legal review or external counsel requests. This is useful when legal teams need evidence of publication timing, approved content, or rights status. By linking operational publishing records to legal matters, organizations reduce manual evidence gathering and improve the quality of legal responses.
Data flow: Bi-directional
Consonance can store workflow decisions related to acquisitions, rights clearance, and publication approvals, while eDOCS stores the authoritative legal documents and annotations. Synchronizing key metadata such as title, author, contract status, matter number, and approval dates creates a complete audit trail across publishing and legal functions. This helps publishers demonstrate governance, support internal audits, and accelerate decision-making across editorial, rights, finance, and legal teams.
Data flow: Consonance to OpenText eDOCS
At the end of a publishing cycle, Consonance can transfer final title files, approved contracts, rights documentation, and publication records into eDOCS for records retention and compliance management. eDOCS is well suited to long-term secure storage and controlled access, while Consonance remains focused on active publishing work. This reduces storage fragmentation, supports retention policies, and ensures critical publishing records remain accessible for future legal or commercial needs.