Home | Connectors | OpenText Magellan Risk Guard | OpenText Magellan Risk Guard - Ziflow Integration and Automation
Data flow: Ziflow ? OpenText Magellan Risk Guard
Creative teams submit ads, social posts, brochures, or campaign copy in Ziflow for review. Before approvers sign off, the content is sent to OpenText Magellan Risk Guard to detect sensitive language, regulatory claims, confidential information, or prohibited terms. If issues are found, the proof is routed back to the creative owner with compliance comments attached.
Business value: Reduces the risk of publishing non-compliant marketing content and shortens the time compliance teams spend on manual review.
Data flow: OpenText Magellan Risk Guard ? Ziflow
When OpenText Magellan Risk Guard identifies high-risk content in a document, it can trigger a Ziflow workflow that routes the proof to legal, compliance, or brand governance reviewers. The proof can be tagged with the risk category, such as privacy, financial claims, or regulated wording, so reviewers know exactly why the item needs attention.
Business value: Ensures risky assets receive the right level of review without slowing down low-risk creative approvals.
Data flow: Bi-directional
Ziflow manages the creative proofing cycle, while OpenText Magellan Risk Guard continuously scans revised versions for compliance issues. Each time a new version is uploaded in Ziflow, it is rechecked by OpenText Magellan Risk Guard. Approval can only proceed when the content passes the risk threshold and all required reviewers have signed off.
Business value: Creates a defensible approval trail for regulated industries such as financial services, healthcare, insurance, and pharmaceuticals.
Data flow: Ziflow ? OpenText Magellan Risk Guard
Before proofs are shared with agencies, freelancers, or external stakeholders through Ziflow, the content is scanned for confidential information such as customer data, internal pricing, unreleased product details, or legal language. If sensitive content is detected, the system can block external sharing or require redaction before release.
Business value: Helps prevent accidental disclosure of confidential or regulated information during creative collaboration.
Data flow: OpenText Magellan Risk Guard ? Ziflow
When OpenText Magellan Risk Guard flags an issue, it can create a remediation task in Ziflow and assign it to the designer, copywriter, or content owner. The task includes the flagged text, risk reason, and required action, such as removing a claim, updating a disclaimer, or replacing a restricted image reference.
Business value: Speeds up correction cycles and reduces back-and-forth between compliance and creative teams.
Data flow: Bi-directional
Ziflow stores the proofing history, reviewer comments, and approval timestamps, while OpenText Magellan Risk Guard contributes risk findings and remediation outcomes. Together, they create a complete audit trail showing what was reviewed, what was flagged, how it was resolved, and who approved the final version.
Business value: Supports internal audits, regulatory inquiries, and governance reporting with clear evidence of control.
Data flow: OpenText Magellan Risk Guard ? Ziflow
OpenText Magellan Risk Guard can assign a risk score to each asset based on detected content issues. Ziflow can use that score to prioritize proofs in the review queue, sending low-risk items through standard approval and high-risk items to senior reviewers or compliance specialists.
Business value: Improves review efficiency by focusing expert attention on the content most likely to create exposure.
Data flow: Ziflow ? OpenText Magellan Risk Guard
After a proof is approved in Ziflow, the final content can still be monitored by OpenText Magellan Risk Guard if it is reused, repurposed, or updated in downstream channels. This is useful when approved copy is later adapted for regional markets, partner campaigns, or new distribution formats where compliance risk may change.
Business value: Extends governance beyond initial approval and helps prevent compliant content from becoming non-compliant after reuse.