Consonance - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Webroot Unity

1. Secure access provisioning for editorial, production, and rights teams

Data flow: Consonance ? OpenText Webroot Unity

When new users are added in Consonance for editors, freelancers, designers, rights managers, or production staff, the integration can automatically trigger endpoint security enrollment or policy assignment in Webroot Unity. This ensures that every device used to access manuscript files, contracts, royalty data, and title metadata is protected before users begin work.

• Automatically apply security policies based on role, imprint, or project sensitivity
• Reduce manual onboarding steps for IT and publishing operations
• Lower the risk of unprotected access to confidential manuscripts and rights information

2. Risk-based protection for high-value manuscript and rights workflows

Data flow: Consonance ? OpenText Webroot Unity

Consonance can flag projects involving embargoed titles, celebrity authors, high-value rights deals, or sensitive acquisition documents. That project context can be sent to Webroot Unity to apply stricter endpoint controls for users working on those assets, such as enhanced malware protection, tighter phishing defenses, or more frequent security checks.

• Increase protection for teams handling pre-publication content
• Support differentiated security for sensitive acquisitions and rights negotiations
• Align endpoint controls with business-critical publishing milestones

3. Security incident alerts tied to publishing project ownership

Data flow: OpenText Webroot Unity ? Consonance

If Webroot Unity detects malware, ransomware, or suspicious activity on a device used by a publisher employee or contractor, the alert can be pushed into Consonance and linked to the affected title, project, or team member. This gives editorial and production managers immediate visibility into whether a manuscript, cover file, or schedule may be at risk.

• Notify project owners when a device used on a title is compromised
• Help teams assess whether manuscript, artwork, or metadata work needs to be paused
• Improve coordination between IT security and publishing operations

4. Controlled access to distribution and metadata updates from secured endpoints

Data flow: Bi-directional

Consonance manages title metadata, schedules, and distribution-ready information, while Webroot Unity validates the security posture of the endpoint used to make those updates. If a device fails security checks, Consonance can restrict sensitive actions such as publishing final metadata, releasing files to distribution partners, or approving last-minute changes.

• Prevent compromised devices from altering retailer-facing metadata
• Reduce the chance of malicious changes to pricing, ISBNs, or publication dates
• Protect downstream distribution and sales channel integrity

5. Secure freelancer and vendor collaboration for design and production assets

Data flow: Consonance ? OpenText Webroot Unity

Publishers often work with external designers, proofreaders, illustrators, and production vendors who access files outside the core corporate network. Consonance can identify external collaborators assigned to a title and send that information to Webroot Unity so their endpoints receive the appropriate security posture before they access shared assets or workflow tasks.

• Extend endpoint protection to non-employee contributors
• Reduce exposure from unmanaged or less secure contractor devices
• Support safer collaboration across distributed publishing teams

6. Incident-driven workflow pauses for affected titles

Data flow: OpenText Webroot Unity ? Consonance

When Webroot Unity identifies a serious threat on a user device, Consonance can automatically place related publishing tasks on hold. For example, if a production editor?s laptop is infected, the system can pause manuscript approvals, cover uploads, or final proof signoff until IT confirms the device is clean.

• Prevent contaminated files from moving through the publishing pipeline
• Reduce operational disruption by clearly identifying impacted projects
• Give publishing managers a structured response process for security events

7. Audit and compliance reporting for content and security governance

Data flow: Bi-directional

Consonance provides workflow history for manuscript handling, approvals, and rights activity, while Webroot Unity provides endpoint security event logs and threat history. Combining both sources creates a stronger audit trail for publishers that need to demonstrate control over sensitive content, third-party access, and production environments.

• Correlate who accessed a title with the security status of the device used
• Support internal audits, publisher governance, and incident reviews
• Improve accountability across editorial, IT, and production teams

8. Protection of royalty and rights operations from phishing and credential compromise

Data flow: OpenText Webroot Unity ? Consonance

Rights and royalty teams often handle bank details, contract terms, and partner communications that are attractive targets for phishing. If Webroot Unity detects a phishing attempt or credential risk on a user account tied to Consonance, the integration can trigger additional verification or temporarily restrict access to royalty and rights modules until the risk is resolved.

• Reduce the chance of fraudulent payment or rights changes
• Protect sensitive partner and author financial information
• Strengthen controls around high-risk publishing transactions