OpenText Directory Services - Centric Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Centric

1. Centralized user provisioning for Centric access

Data flow: OpenText Directory Services ? Centric

Use OpenText Directory Services as the authoritative identity source to automatically provision Centric users, assign roles, and maintain group membership. When employees join a design, product development, or quality team, their Centric access can be created based on directory attributes such as department, location, or job function.

Business value: Reduces manual account setup, speeds onboarding, and ensures users receive the correct access from day one.

2. Automated deprovisioning when employees leave or change roles

Data flow: OpenText Directory Services ? Centric

When a user is disabled, moved to another department, or removed from a project group in OpenText Directory Services, Centric access can be updated automatically. This includes disabling accounts, removing project permissions, or adjusting role-based access to product data and collaboration spaces.

Business value: Improves security, reduces orphaned accounts, and supports compliance with internal access control policies.

3. Role-based access control for product development teams

Data flow: Bi-directional, with OpenText Directory Services as the identity master and Centric consuming role assignments

Synchronize directory groups with Centric roles to control access for designers, product managers, sourcing teams, and approvers. For example, a ?Footwear Design? group in OpenText Directory Services can map to a corresponding Centric project role with permissions to view, edit, or approve product specifications.

Business value: Ensures consistent access governance across teams and reduces the risk of unauthorized changes to product records.

4. Project team access synchronization for seasonal or launch programs

Data flow: OpenText Directory Services ? Centric

For time-bound product initiatives such as seasonal collections or new product launches, directory groups can be used to automatically grant Centric access to temporary project teams. When the launch ends, removing users from the directory group can revoke access in Centric without manual cleanup.

Business value: Simplifies project administration and supports rapid team changes common in product development cycles.

5. Shared identity governance across design and product lifecycle workflows

Data flow: Bi-directional

Use OpenText Directory Services to maintain a single identity record while Centric reflects user participation in product workflows such as concept review, sample approval, and specification sign-off. Centric can send workflow participation or approval status back to directory-linked reporting structures for audit and governance purposes.

Business value: Creates a clearer audit trail for who participated in key product decisions and supports governance across cross-functional teams.

6. Synchronization of organizational changes into Centric collaboration spaces

Data flow: OpenText Directory Services ? Centric

When organizational structures change, such as a new product line, regional team, or reporting hierarchy, those updates can be reflected in Centric collaboration spaces and access groups. This helps ensure that product development workspaces stay aligned with the current operating model.

Business value: Reduces administrative lag after reorganizations and keeps collaboration structures aligned with the business.

7. Secure external partner access for product development collaboration

Data flow: OpenText Directory Services ? Centric

For agencies, suppliers, or contract designers who need limited Centric access, OpenText Directory Services can manage partner identities and group membership while Centric applies restricted permissions to specific projects or product folders. Access can be time-limited and tied to approved partner groups.

Business value: Enables controlled external collaboration while maintaining strong access governance and reducing security risk.

8. Directory-driven audit support for product compliance reviews

Data flow: Bi-directional

Use OpenText Directory Services to provide authoritative user and group data for Centric audit reviews, helping compliance teams verify who had access to product records, approvals, and design assets at a given time. Centric can contribute workflow and approval activity to support investigations or regulatory checks.

Business value: Strengthens traceability, supports compliance audits, and improves accountability across the product lifecycle.