OpenText Lens - Data Visibility - OpenText Identity and Access Management Integration and Automation

Common Integration Use Cases Between OpenText Lens - Data Visibility and OpenText Identity and Access Management

1. Role-Based Access for Sensitive Data Discovery Reports

Data flow: OpenText Lens - Data Visibility → OpenText Identity and Access Management

OpenText Lens identifies sensitive, regulated, or high-risk content across repositories, then passes classification results to OpenText Identity and Access Management to control who can view reports, dashboards, and remediation queues. Security, legal, and data governance teams can be assigned access based on role, region, or business unit.

Business value: Limits exposure of sensitive findings, supports least-privilege access, and ensures only authorized teams can act on data risk insights.

2. Automated Access Provisioning for Data Governance Teams

Data flow: OpenText Identity and Access Management → OpenText Lens - Data Visibility

When new users are added to governance, compliance, or records management roles in OpenText Identity and Access Management, access to OpenText Lens projects, scans, and exception workflows is automatically provisioned. When users change roles or leave the organization, access is removed without manual intervention.

Business value: Reduces administrative overhead, shortens onboarding time, and prevents orphaned access to data visibility tools.

3. Segregated Review Workflows for Sensitive Content Remediation

Data flow: OpenText Lens - Data Visibility → OpenText Identity and Access Management

OpenText Lens flags sensitive or obsolete content and routes remediation tasks to the appropriate reviewers. OpenText Identity and Access Management enforces role-based approval paths so that only designated data owners, privacy officers, or legal reviewers can approve deletion, retention, or migration decisions.

Business value: Improves accountability in remediation workflows, supports auditability, and reduces the risk of unauthorized content disposition.

4. Secure Self-Service Access to Repository Visibility for Business Owners

Data flow: OpenText Identity and Access Management → OpenText Lens - Data Visibility

Business owners can authenticate through single sign-on and receive access to Lens views that show only the repositories, folders, or content domains they are responsible for. This allows decentralized teams to review their own data footprint without requiring IT to manually grant access each time.

Business value: Increases adoption of data governance programs, accelerates business-led cleanup, and reduces dependency on central IT.

5. Compliance Evidence Collection with Controlled Auditor Access

Data flow: OpenText Lens - Data Visibility → OpenText Identity and Access Management

Lens produces evidence such as data inventories, sensitive content counts, and repository risk summaries. Identity and Access Management restricts auditor access to approved time windows and specific compliance artifacts, ensuring external auditors or internal control teams only see what they are authorized to review.

Business value: Strengthens compliance controls, simplifies audit preparation, and reduces the risk of overexposing enterprise content intelligence.

6. Migration Readiness Reviews with Access-Controlled Stakeholder Collaboration

Data flow: OpenText Lens - Data Visibility → OpenText Identity and Access Management

Before migrating content to a new OpenText environment or another repository, Lens identifies redundant, obsolete, and sensitive data. Identity and Access Management then controls which migration planners, application owners, and approvers can review the findings and sign off on what should move, be retained, or be deleted.

Business value: Reduces migration scope, lowers storage and licensing costs, and ensures only approved stakeholders influence migration decisions.

7. Incident Response Access for High-Risk Data Exposure Investigations

Data flow: OpenText Lens - Data Visibility → OpenText Identity and Access Management

When Lens detects unusual concentrations of sensitive data or obsolete content in exposed repositories, it can trigger restricted incident review access for security and privacy teams through Identity and Access Management. Access can be time-bound and limited to the affected repositories and investigation team members.

Business value: Speeds response to data exposure risks, supports controlled investigations, and helps contain potential compliance incidents.

8. Centralized Identity Governance for Multi-Repository Data Cleanup Programs

Data flow: Bi-directional

Lens identifies where sensitive or stale content exists across multiple repositories, while Identity and Access Management ensures that only approved users can initiate cleanup actions, view exception lists, or approve retention changes. Access policies can be aligned to repository ownership, geography, or regulatory requirements.

Business value: Enables large-scale cleanup programs with strong governance, improves cross-team coordination, and reduces operational risk during data remediation.