OpenText Core Signature - OpenText Magellan Risk Guard Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and OpenText Magellan Risk Guard

1. Pre-signature content risk screening for contracts and agreements

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

Before a document is routed for signature, the agreement text is scanned by Magellan Risk Guard to identify risky clauses, sensitive data, prohibited language, or compliance exceptions. If issues are detected, the document is held for review before signature is allowed.

• Reduces the risk of signing non-compliant or legally problematic documents
• Improves contract governance and approval quality
• Supports legal, compliance, and procurement teams with a controlled review step

2. Signed document compliance validation and exception handling

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

After a document is signed, the final executed version is sent to Magellan Risk Guard for compliance validation. The system checks for sensitive disclosures, restricted terms, or policy violations in the signed content and flags exceptions for remediation or escalation.

• Creates a post-signature control to catch issues missed earlier in the workflow
• Helps organizations maintain audit-ready records
• Supports legal and risk teams in identifying documents requiring corrective action

3. Sensitive data detection in customer onboarding documents

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

During customer onboarding, signed forms such as applications, disclosures, and consent documents are analyzed to detect personal data, financial information, or regulated content that may require special handling. Findings can trigger retention rules, redaction workflows, or compliance review.

• Improves privacy and data handling controls
• Reduces exposure of sensitive customer information
• Supports onboarding teams, compliance officers, and records management

4. HR document review for policy and privacy risks

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

Employment agreements, policy acknowledgements, and HR forms signed through Core Signature are passed to Magellan Risk Guard to detect problematic clauses, confidential employee data, or inconsistent policy language. This helps HR and legal teams identify documents that may need correction or escalation.

• Strengthens HR compliance and employee privacy protection
• Helps standardize employment documentation
• Reduces legal exposure from outdated or non-compliant templates

5. Legal approval workflow with automated risk escalation

Data flow: Bi-directional

Magellan Risk Guard flags risky language in draft documents and sends the findings to the legal or contract owner. Once the issues are resolved, the document is routed to Core Signature for execution. If the signed version still contains exceptions, the risk findings are fed back to the legal team for follow-up.

• Creates a closed-loop review and approval process
• Improves turnaround time for legal sign-off
• Ensures risk findings directly influence signature readiness

6. Controlled signing of regulated disclosures and notices

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

Regulated documents such as disclosures, consent notices, or customer communications are signed in Core Signature and then screened in Magellan Risk Guard to confirm that required language is present and no prohibited statements were introduced. This is especially useful in financial services, healthcare, and insurance.

• Supports regulatory consistency across high-volume documents
• Helps prove that approved language was used
• Reduces the chance of non-compliant customer communications

7. Audit and remediation workflow for signed records

Data flow: OpenText Core Signature ? OpenText Magellan Risk Guard

Signed records are periodically analyzed by Magellan Risk Guard to identify documents that contain sensitive terms, outdated clauses, or content requiring retention, redaction, or restricted access. The results can trigger remediation tasks in records, legal, or compliance workflows.

• Improves ongoing governance of executed documents
• Supports audit preparation and records remediation
• Helps organizations manage signed content at scale

8. Exception-based approval routing for high-risk documents

Data flow: OpenText Magellan Risk Guard ? OpenText Core Signature

When Magellan Risk Guard identifies a document as high risk, the integration can block automatic signature routing and instead send the document to a designated approver, such as legal, compliance, or a senior manager. Only after approval is the document released to Core Signature for execution.

• Prevents premature signing of risky documents
• Enforces policy-based approval thresholds
• Improves accountability across business and control functions