Common Integration Use Cases Between OpenText Directory Services and Plytix
1. Centralized user provisioning for Plytix from OpenText Directory Services
Use OpenText Directory Services as the master identity source to automatically create, update, and deactivate Plytix user accounts. This ensures product managers, catalog editors, and external contributors receive the right access without manual onboarding.
- Data flow: OpenText Directory Services to Plytix
- Business value: Faster onboarding, reduced admin effort, and lower risk of orphaned accounts
- Typical outcome: New employees are assigned Plytix access based on their directory profile and role
2. Role-based access control for product data teams
Synchronize groups and roles from OpenText Directory Services into Plytix to control who can edit, approve, or publish product information. This is useful for separating responsibilities across merchandising, marketing, operations, and external agencies.
- Data flow: OpenText Directory Services to Plytix
- Business value: Stronger governance over product content and fewer unauthorized changes
- Typical outcome: Only approved users can publish product records to downstream channels
3. Automated access removal when employees leave or change roles
When a user is disabled or moved to a different department in OpenText Directory Services, the corresponding Plytix access can be revoked or adjusted automatically. This supports security and compliance while reducing manual cleanup work for IT and business admins.
- Data flow: OpenText Directory Services to Plytix
- Business value: Improved security posture and consistent access lifecycle management
- Typical outcome: Departing employees lose Plytix access immediately, and role changes trigger updated permissions
4. Synchronization of organizational structure for workflow assignment
Import department, team, or location attributes from OpenText Directory Services into Plytix to route product enrichment tasks to the right business owners. This helps assign catalog maintenance responsibilities by region, brand, or business unit.
- Data flow: OpenText Directory Services to Plytix
- Business value: Clear ownership of product data and faster task resolution
- Typical outcome: Product records for a specific brand are automatically assigned to the correct regional team
5. Shared identity governance across OpenText and product operations
Use OpenText Directory Services to maintain a single identity and access model for teams working in both OpenText environments and Plytix. This reduces duplicate account management and gives IT a consistent view of who has access to product information systems.
- Data flow: Bi-directional governance alignment, with OpenText Directory Services as the system of record for identities
- Business value: Simplified administration and consistent policy enforcement across platforms
- Typical outcome: The same employee identity and group membership rules apply across enterprise content and product data workflows
6. Secure external partner access to Plytix through controlled directory groups
For agencies, distributors, or contractors who need limited access to product data, OpenText Directory Services can manage partner identities and group membership, then provision only the required Plytix permissions. This supports controlled collaboration without exposing the full catalog environment.
- Data flow: OpenText Directory Services to Plytix
- Business value: Safer partner collaboration and reduced risk of overexposure of sensitive product information
- Typical outcome: An agency can edit marketing descriptions but cannot change pricing or publish records
7. Audit-ready access reporting for product information governance
Combine directory records from OpenText Directory Services with Plytix user access data to support audits, access reviews, and compliance checks. This helps security and operations teams verify who can access product data and whether permissions match current job responsibilities.
- Data flow: Bi-directional reporting and reconciliation
- Business value: Better audit readiness and stronger internal controls
- Typical outcome: Quarterly access reviews identify inactive users, excessive permissions, or outdated group assignments