Cloudinary - OpenText Lens - Data Visibility Integration and Automation

Common Integration Use Cases Between Cloudinary and OpenText Lens - Data Visibility

1. Identify and remediate ungoverned media assets before publishing

Data flow: OpenText Lens - Data Visibility to Cloudinary

OpenText Lens scans shared drives, content repositories, and collaboration platforms to identify image and video files that are redundant, obsolete, or potentially sensitive. Approved assets can then be moved into Cloudinary for controlled transformation, optimization, and delivery. This helps marketing and web teams avoid publishing unmanaged media while giving governance teams visibility into what is entering the media pipeline.

• Reduces risk of using outdated or unauthorized assets
• Improves media governance before assets reach customer-facing channels
• Creates a cleaner, standardized asset library in Cloudinary

2. Support migration of legacy media libraries into a modern delivery platform

Data flow: OpenText Lens - Data Visibility to Cloudinary

During a digital modernization or CMS migration, OpenText Lens can inventory legacy repositories to determine which media files are active, duplicate, or obsolete. The business can then migrate only the relevant images and videos into Cloudinary, reducing storage costs and migration effort. This is especially useful when consolidating multiple brand sites, regional portals, or legacy DAM systems.

• Minimizes migration scope and cost
• Helps teams prioritize high-value assets for Cloudinary onboarding
• Improves migration planning with data-driven inventory insights

3. Detect sensitive content in user-generated media before public delivery

Data flow: Cloudinary to OpenText Lens - Data Visibility

When organizations accept user-uploaded images or videos through Cloudinary, those assets can be forwarded to OpenText Lens for analysis to identify potentially sensitive or noncompliant content stored in connected repositories or downstream archives. This is valuable for regulated industries, online communities, and customer portals that must monitor media for privacy, legal, or policy concerns.

• Supports compliance and content risk management
• Helps teams flag media that may require review or retention controls
• Improves oversight of user-generated content at scale

4. Classify and rationalize duplicate media across business units

Data flow: OpenText Lens - Data Visibility to Cloudinary

OpenText Lens can identify duplicate or near-duplicate media files across departments, regions, or business units. Once the authoritative version is selected, that asset can be centralized in Cloudinary for reuse across websites, campaigns, and applications. This reduces storage sprawl and ensures teams are using the same approved media variants.

• Eliminates duplicate asset storage and manual version tracking
• Improves brand consistency across channels
• Enables reuse of approved media variants from a single source

5. Improve retention and lifecycle management for media archives

Data flow: Bi-directional

Cloudinary can serve as the active delivery layer for current media, while OpenText Lens analyzes older repositories and archives to determine what content is still needed, what can be archived, and what should be deleted. Metadata or classification results from Lens can be used to define retention rules, while Cloudinary usage patterns can help identify which assets remain business-critical.

• Supports defensible deletion and retention decisions
• Reduces long-term storage and compliance exposure
• Helps records and IT teams align on media lifecycle policies

6. Accelerate content cleanup before website or application redesigns

Data flow: OpenText Lens - Data Visibility to Cloudinary

Before a web redesign, replatforming, or mobile app refresh, OpenText Lens can analyze existing media repositories to identify obsolete banners, outdated product images, and unused video files. The approved set can then be migrated into Cloudinary for responsive delivery and transformation across the new experience. This helps project teams avoid carrying unnecessary content into the new platform.

• Reduces content clutter during redesign projects
• Speeds up launch by focusing only on relevant assets
• Ensures optimized media is ready for the new digital experience

7. Establish a governed media intake process for enterprise content operations

Data flow: Cloudinary and OpenText Lens - Data Visibility

Organizations can use OpenText Lens to assess incoming media from business repositories and route approved assets into Cloudinary, where they are optimized and delivered to digital channels. This creates a controlled intake workflow for marketing, ecommerce, and communications teams, with governance checks occurring before assets are exposed externally.

• Creates a repeatable approval workflow for media assets
• Improves collaboration between governance, marketing, and IT teams
• Ensures only validated assets are published through Cloudinary

8. Reduce risk in regulated industries by linking media visibility with delivery controls

Data flow: Bi-directional

In regulated sectors such as healthcare, financial services, or public sector, OpenText Lens can identify sensitive media stored across repositories, while Cloudinary manages how approved media is transformed and delivered. Together, they help organizations control what media exists, where it is stored, and how it is published to external audiences. This supports audit readiness, policy enforcement, and faster response to content-related risk.

• Improves auditability of media assets across the enterprise
• Supports compliance reviews and risk mitigation
• Aligns content governance with digital delivery operations