OpenText Lens - Data Visibility - OpenText Core Experience Insights Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and OpenText Core Experience Insights

1. Content Cleanup Prioritization Based on Actual User Engagement

Data flow: OpenText Core Experience Insights ? OpenText Lens - Data Visibility

Use interaction analytics to identify content that is rarely accessed, abandoned, or no longer relevant, then feed those findings into OpenText Lens - Data Visibility to validate whether the content should be retained, archived, or deleted.

• Business value: Reduces storage and governance overhead by focusing cleanup on low-value content.
• Operational benefit: Information governance teams can prioritize remediation using evidence of low usage instead of manual review.
• Example: A legal department identifies thousands of policy documents with no views in 18 months and uses Lens to confirm duplicates and obsolete versions before disposition.

2. Sensitive Content Exposure Monitoring in High-Usage Areas

Data flow: OpenText Lens - Data Visibility ? OpenText Core Experience Insights

Use Lens to detect sensitive or regulated content in repositories, then correlate that content with usage patterns in Core Experience Insights to determine whether high-risk documents are being actively accessed by broad user groups.

• Business value: Helps reduce compliance and privacy risk by identifying sensitive content that is both exposed and frequently used.
• Operational benefit: Security, compliance, and business owners can target remediation where risk is highest.
• Example: A finance team discovers confidential spreadsheets in a shared workspace and sees repeated access from non-finance users, triggering permission review and content relocation.

3. Migration Readiness and Adoption Planning

Data flow: OpenText Lens - Data Visibility ? OpenText Core Experience Insights

Before a content migration or platform consolidation, use Lens to inventory and classify content, then use Core Experience Insights to understand which repositories, folders, and content types are most actively used so migration waves can be sequenced around business criticality.

• Business value: Lowers migration risk and improves user adoption by protecting high-value content and workflows.
• Operational benefit: Migration teams can separate active content from stale content and plan cutover timing more effectively.
• Example: During a move to a new digital workplace, the project team migrates heavily used collaboration spaces first and archives inactive project sites identified by Lens.

4. Governance Exception Management for Frequently Used Content

Data flow: Bi-directional

When Lens flags content as redundant, obsolete, or sensitive, Core Experience Insights can show whether that content is still essential to daily work. This allows governance teams to create exceptions for business critical content that should not be removed immediately.

• Business value: Prevents disruption by balancing governance controls with real user needs.
• Operational benefit: Reduces false positives in cleanup and improves stakeholder trust in governance decisions.
• Example: A set of outdated templates is flagged for removal, but usage analytics show they are still heavily used by a regional sales team, so the team updates the templates before retirement.

5. Repository Rationalization and Workspace Consolidation

Data flow: OpenText Core Experience Insights ? OpenText Lens - Data Visibility

Use Core Experience Insights to identify underused sites, workspaces, and content collections, then use Lens to inspect the underlying content for duplication, sensitivity, and retention issues before consolidating or decommissioning them.

• Business value: Cuts operational cost by reducing the number of inactive or redundant repositories.
• Operational benefit: IT and business owners can rationalize content environments with better evidence and less manual review.
• Example: An enterprise discovers several departmental workspaces with minimal activity and uses Lens to confirm that most content is duplicated elsewhere before merging them into a single shared repository.

6. Compliance Reporting with Usage Context

Data flow: Bi-directional

Combine Lens classification results with Core Experience Insights usage metrics to produce compliance reports that show not only where regulated content exists, but also how often it is accessed and by whom.

• Business value: Improves audit readiness and supports stronger risk-based compliance decisions.
• Operational benefit: Compliance teams can prioritize controls for content that is both sensitive and heavily used.
• Example: A healthcare organization reports on patient-related documents stored across repositories and highlights the most accessed collections for additional access control review.

7. User Experience Improvement for Content Governance Actions

Data flow: OpenText Core Experience Insights ? OpenText Lens - Data Visibility

Analyze user behavior to identify where people struggle to find or use content, then use Lens to determine whether the issue is caused by duplicate versions, poor content quality, or excessive obsolete content cluttering search results.

• Business value: Improves employee productivity by making content easier to find and trust.
• Operational benefit: Information architects and content owners can fix root causes instead of only addressing symptoms.
• Example: Search analytics show repeated access failures for a key procedure document, and Lens reveals multiple outdated copies across repositories, prompting consolidation and metadata cleanup.

8. Continuous Improvement for Records and Retention Programs

Data flow: Bi-directional

Use Lens to identify content that qualifies for retention review or disposition, and use Core Experience Insights to monitor whether users continue to rely on that content after policy changes or cleanup actions. This supports ongoing tuning of retention schedules and governance rules.

• Business value: Creates a feedback loop that improves records management decisions over time.
• Operational benefit: Records managers can validate policy changes against real usage patterns and adjust governance rules accordingly.
• Example: After a retention policy update, the organization monitors whether access to archived project records drops as expected or whether business teams still depend on them for operational reference.