OpenText Directory Services - DeSL Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and DeSL

1. Centralized user provisioning for DeSL from OpenText Directory Services

Data flow: OpenText Directory Services ? DeSL

Use OpenText Directory Services as the authoritative identity source to automatically create, update, and deactivate DeSL user accounts for designers, product developers, merchandisers, sourcing teams, and external partners. This reduces manual onboarding effort and ensures users receive the correct access as soon as they join a project or business unit.

• Automates account creation for new hires and contractors
• Removes access quickly when users leave or change roles
• Reduces help desk tickets related to access setup

2. Role-based access control for product development workflows

Data flow: OpenText Directory Services ? DeSL

Synchronize directory groups and roles into DeSL so access to product lines, collections, and workflow stages is assigned based on business function. For example, design teams can edit tech packs, sourcing teams can view supplier data, and executives can access reporting only. This improves governance and limits unauthorized changes to product records.

• Aligns access with organizational roles and project teams
• Supports segregation of duties across PLM processes
• Improves auditability for sensitive product and supplier data

3. Automatic access updates when employees change departments or brands

Data flow: OpenText Directory Services ? DeSL

When a user moves from one department, brand, or region to another, OpenText Directory Services can update group membership and trigger corresponding access changes in DeSL. This is especially useful in fashion organizations where teams frequently shift across seasons, collections, and regional business units.

• Prevents users from retaining outdated access
• Ensures current project and brand permissions are applied quickly
• Supports organizational changes without manual rework

4. External partner and supplier collaboration access management

Data flow: Bi-directional

Use OpenText Directory Services to manage identities for external suppliers, factories, and design partners collaborating in DeSL. DeSL can then use those identities to control access to shared product specifications, sample approvals, and sourcing workflows. This creates a controlled collaboration model for third parties while maintaining enterprise governance.

• Provides secure access for vendors and manufacturing partners
• Limits visibility to only the products and documents relevant to each partner
• Improves collaboration without exposing internal-only data

5. Single sign-on for DeSL users through enterprise identity services

Data flow: OpenText Directory Services ? DeSL

Integrate authentication so users sign in to DeSL using their enterprise credentials managed in OpenText Directory Services. This simplifies access for internal teams working across multiple systems and reduces password-related support issues. It also strengthens security by centralizing authentication policies.

• Improves user experience with one set of credentials
• Supports stronger password and access policies
• Reduces account duplication across systems

6. Project team access synchronization for seasonal product launches

Data flow: OpenText Directory Services ? DeSL

Fashion and retail organizations often create temporary teams for seasonal launches, capsule collections, or regional assortments. Directory groups can be mapped into DeSL project access so users are automatically added to the correct product development workspace for the duration of the initiative and removed when the project closes.

• Speeds setup of new collection teams
• Ensures timely access to design and sourcing workspaces
• Reduces cleanup effort after launch completion

7. Access governance and audit reporting for PLM operations

Data flow: DeSL ? OpenText Directory Services

DeSL can send user activity or role assignment information back to OpenText Directory Services or a connected governance process to support access reviews and compliance audits. This helps security and business teams verify who has access to product data, supplier records, and workflow approvals, especially in regulated or highly competitive retail environments.

• Supports periodic access certification
• Improves visibility into who can approve or modify product data
• Helps meet internal audit and compliance requirements

8. Lifecycle-based deprovisioning after project or contract end

Data flow: OpenText Directory Services ? DeSL

When a contractor, freelancer, or supplier relationship ends, OpenText Directory Services can trigger account disablement in DeSL and remove access to active product lines, documents, and collaboration spaces. This is critical for protecting intellectual property and preventing unauthorized access after engagement ends.

• Reduces security risk from stale accounts
• Protects confidential designs and sourcing information
• Ensures access is removed consistently across teams and regions