OpenText Core Signature - OpenText Webroot Unity Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and OpenText Webroot Unity

OpenText Core Signature and OpenText Webroot Unity address different but complementary enterprise needs: secure digital approvals and endpoint cybersecurity. Integrating them can help organizations reduce risk during document-driven workflows, protect users involved in signing processes, and improve governance across business and security teams.

1. Secure employee onboarding with protected signing devices

Flow: OpenText Webroot Unity to OpenText Core Signature

When HR initiates onboarding, Webroot Unity can verify that the employee?s laptop or mobile device meets security standards before the onboarding packet is sent for signature in Core Signature. If the device is flagged for malware, outdated protection, or suspicious activity, the signing workflow can be delayed or redirected to a secure device.

• Reduces risk of credential theft during onboarding
• Ensures sensitive HR documents are signed from trusted endpoints
• Improves compliance for remote and hybrid hiring

2. Risk-based approval of high-value contracts

Flow: Bi-directional

For contracts above a certain value or involving regulated data, Core Signature can trigger a security check through Webroot Unity before the document is released for signature. If Webroot detects an endpoint threat on the approver?s device, the workflow can pause and notify procurement or legal teams to use a safer device or alternate approval path.

• Prevents contract execution from compromised endpoints
• Supports stronger controls for legal and procurement approvals
• Creates an auditable link between security status and signature authorization

3. Protected customer onboarding and account opening

Flow: OpenText Webroot Unity to OpenText Core Signature

In customer onboarding, sales or operations teams can use Webroot Unity to validate the security posture of internal devices used to prepare and send agreements through Core Signature. This is especially useful for financial services, insurance, and healthcare organizations handling sensitive personal data.

• Reduces exposure of customer data during document preparation
• Helps maintain trust in digital onboarding processes
• Supports secure remote sales and service operations

4. Incident-driven suspension of signature workflows

Flow: OpenText Webroot Unity to OpenText Core Signature

If Webroot Unity detects ransomware, phishing, or other endpoint threats on a user?s device, it can automatically suspend active signature workflows in Core Signature for that user. This prevents compromised accounts from approving documents, sending signature requests, or accessing sensitive agreements until the device is remediated.

• Limits fraud and unauthorized approvals
• Reduces the chance of malicious document tampering
• Improves response time during security incidents

5. Secure legal and compliance review of sensitive documents

Flow: Bi-directional

Legal and compliance teams often review contracts, policy updates, and regulated documents on endpoints that may access external email and web content. Webroot Unity can continuously assess endpoint risk, while Core Signature manages the controlled review and approval process. If a reviewer?s device becomes high risk, the document can be reassigned or held until the endpoint is cleared.

• Protects sensitive policy and legal content
• Maintains continuity in approval chains
• Supports governance for regulated document workflows

6. Conditional signing for privileged access and IT requests

Flow: OpenText Core Signature to OpenText Webroot Unity

Organizations can require signed approval for privileged access requests, software exceptions, or security policy acknowledgments in Core Signature, then use Webroot Unity to verify that the requester?s endpoint is compliant before the request is fulfilled. This is useful for IT service management and security operations teams.

• Ensures approvals are completed before access is granted
• Reduces risk from unmanaged or infected endpoints
• Improves control over exceptions and privileged actions

7. Audit-ready evidence for regulated workflows

Flow: Bi-directional

Core Signature can provide the signed document trail, while Webroot Unity can provide endpoint security status at the time of signing. Together, they create a stronger audit package for internal audit, external compliance reviews, and legal disputes by showing both who signed and whether the device environment was secure.

• Strengthens evidentiary records for audits
• Supports compliance in regulated industries
• Improves defensibility of digital approvals

These integrations are most valuable where document approval and endpoint security intersect, such as HR, legal, procurement, finance, and customer onboarding. By combining trusted e-signature workflows with endpoint risk intelligence, organizations can reduce operational friction while improving control and compliance.