Home | Connectors | OpenText Legal Hold | OpenText Legal Hold - IntelligenceBank Integration and Automation
OpenText Legal Hold is designed to preserve relevant information for litigation, investigations, and regulatory matters, while IntelligenceBank is typically used as a marketing and brand asset management platform with strong governance, approval, and content control capabilities. Together, they can help legal, compliance, and marketing teams coordinate on content preservation, review, and controlled access to business-critical assets.
Data flow: OpenText Legal Hold to IntelligenceBank
When a legal hold is issued for a campaign, brand asset, or product launch, OpenText Legal Hold can notify IntelligenceBank to flag the related assets as restricted. This prevents deletion, replacement, or unauthorized editing of files such as creative briefs, artwork, campaign videos, and approval records. The business value is reduced legal risk and faster compliance with preservation obligations without relying on manual intervention from marketing teams.
Data flow: Bi-directional
OpenText Legal Hold maintains custodians tied to a matter, while IntelligenceBank tracks asset owners, reviewers, and approvers. Integrating the two systems allows legal teams to identify which IntelligenceBank users are custodians for a matter and allows IntelligenceBank to return ownership and approval metadata. This improves hold accuracy, reduces missed custodians, and helps legal teams target the right users and content repositories.
Data flow: OpenText Legal Hold to IntelligenceBank
If a file or campaign is under legal hold, IntelligenceBank can automatically suspend related approval workflows, publishing steps, or version promotion for that asset. This is especially useful for regulated industries where a held asset must not be modified or released while an investigation is active. The result is fewer compliance breaches and less manual coordination between legal and marketing operations.
Data flow: IntelligenceBank to OpenText Legal Hold
IntelligenceBank can expose metadata, asset links, version history, and approval trails to OpenText Legal Hold so legal teams can quickly review the exact content associated with a matter. Instead of requesting files from multiple business users, legal can access a governed record of the asset, its revisions, and who approved it. This shortens response times during discovery and internal investigations.
Data flow: Bi-directional
OpenText Legal Hold can send hold status and preservation timestamps to IntelligenceBank, while IntelligenceBank can return audit events such as uploads, edits, approvals, and downloads. Together, these records create a stronger chain of custody for content that may become evidence. This supports defensible legal processes and improves audit readiness for compliance teams.
Data flow: IntelligenceBank to OpenText Legal Hold
IntelligenceBank can provide repository, folder, or asset classification data to help legal teams identify content areas that are likely to be relevant in a matter, such as product claims, regulated messaging, or regional campaign materials. OpenText Legal Hold can then apply holds more precisely to the right custodians and content sets. This reduces over-preservation and lowers the operational burden on the business.
Data flow: OpenText Legal Hold to IntelligenceBank
When a matter is closed, OpenText Legal Hold can notify IntelligenceBank to release the hold on specific assets, folders, or users. IntelligenceBank can then restore normal lifecycle actions, including editing, archiving, or deletion according to policy. This ensures content is retained only as long as required and helps teams return to standard operations quickly after litigation or investigation ends.
These integration scenarios are most valuable in organizations where legal, compliance, and marketing teams manage shared content that may become subject to regulatory review, litigation, or internal investigations. The integration helps preserve evidence, reduce manual coordination, and maintain governance across the content lifecycle.