inriver - OpenText Directory Services Integration and Automation

Common Integration Use Cases Between inriver and OpenText Directory Services

inriver and OpenText Directory Services complement each other by connecting product information management with centralized identity and access management. inriver governs the creation, enrichment, and distribution of product data, while OpenText Directory Services manages users, groups, and role-based access across OpenText environments. Integrating them helps organizations control who can create, approve, localize, and publish product content, improving governance, reducing manual administration, and supporting secure cross-team collaboration.

1. Role-Based Access Provisioning for Product Content Teams

Data flow: OpenText Directory Services → inriver

Synchronize users and groups from OpenText Directory Services into inriver to automatically assign access based on job function, department, or region. For example, product managers can be granted edit rights, legal reviewers can be assigned approval permissions, and regional marketers can be limited to localized content for their market.

• Reduces manual user setup in inriver
• Ensures consistent access control across teams
• Supports least-privilege governance for sensitive product data

2. Automated Onboarding and Offboarding of PIM Users

Data flow: OpenText Directory Services → inriver

When employees join, change roles, or leave the organization, directory updates can automatically create, modify, or disable their inriver accounts. This is especially useful for large product organizations with frequent staffing changes across merchandising, marketing, and operations teams.

• Speeds up onboarding for new product contributors
• Removes access promptly when employees exit
• Reduces security and compliance risks

3. Group-Based Workflow Assignment for Product Approval Processes

Data flow: OpenText Directory Services → inriver

Use directory groups to drive workflow assignments in inriver. For instance, a ?North America Marketing? group can be mapped to review tasks for U.S. and Canadian product launches, while a ?Regulatory Review? group can receive approval tasks for compliance-sensitive items such as food, medical, or industrial products.

• Improves routing accuracy for approvals
• Supports regional and functional review structures
• Shortens product launch cycles by reducing manual task assignment

4. Centralized Identity Management for Multi-Application Product Operations

Data flow: OpenText Directory Services → inriver

Organizations using multiple OpenText and enterprise applications can use OpenText Directory Services as the central identity source and extend that identity to inriver. This creates a consistent user experience for product teams that need access to both content management and product information workflows.

• Reduces duplicate identity administration
• Supports standardized access policies across systems
• Improves auditability of user access to product data

5. Regional Content Localization Access Control

Data flow: OpenText Directory Services → inriver

For global manufacturers and retailers, directory attributes such as region, language, or business unit can be used to control which localized product records users can view or edit in inriver. This helps ensure that local teams only work on the product content relevant to their market while central teams retain oversight.

• Prevents unauthorized edits across markets
• Supports localized product publishing processes
• Helps maintain consistency in global product data

6. Secure Access for External Agencies and Contractors

Data flow: OpenText Directory Services → inriver

Marketing agencies, translators, and content contractors often need temporary access to product information workflows. OpenText Directory Services can manage these external identities and groups, then provision controlled access into inriver for specific projects, brands, or product lines.

• Enables time-bound access for third parties
• Limits exposure to only relevant product data
• Improves governance over outsourced content work

7. Audit-Ready Access Governance for Product Data Stewardship

Data flow: Bi-directional, with OpenText Directory Services as identity source and inriver as access consumer

Integrate directory records with inriver permissions to support audits of who had access to product data, when access was granted, and which groups were responsible for approvals. This is valuable for regulated industries where product claims, labeling, and compliance content must be traceable.

• Supports internal and external audits
• Improves accountability for product changes
• Helps demonstrate control over regulated content

In summary, integrating inriver with OpenText Directory Services strengthens governance around product information by aligning user access, approval workflows, and regional responsibilities with centralized identity management. The result is faster onboarding, better security, cleaner administration, and more reliable collaboration across product, marketing, compliance, and regional teams.