OpenText Directory Services - Ziflow Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and Ziflow

OpenText Directory Services provides centralized identity and access management for enterprise users and groups, while Ziflow manages creative proofing, review, and approval workflows. Integrating the two platforms helps organizations control who can access content, automate user provisioning, and align approval workflows with enterprise roles and teams.

1. Automated user provisioning for creative review teams

Data flow: OpenText Directory Services to Ziflow

When new employees, contractors, or agency users are added to OpenText Directory Services, their accounts can be automatically created in Ziflow with the correct role and permissions. This ensures reviewers, approvers, and project stakeholders are available in Ziflow without manual setup.

• Reduces onboarding time for creative and marketing teams
• Eliminates manual user creation errors
• Ensures access is aligned to enterprise identity records

2. Automatic deprovisioning when users leave the organization

Data flow: OpenText Directory Services to Ziflow

When a user is disabled or removed from OpenText Directory Services, their Ziflow access can be revoked automatically. This is especially useful for agencies, freelancers, and temporary staff who should lose access immediately when their engagement ends.

• Improves security and access governance
• Prevents orphaned accounts in Ziflow
• Supports compliance with internal offboarding controls

3. Role-based access assignment for proofing workflows

Data flow: OpenText Directory Services to Ziflow

Directory groups in OpenText Directory Services can be mapped to Ziflow roles such as reviewer, approver, project owner, or admin. For example, members of a marketing leadership group can be granted approval rights, while agency users are limited to commenting only.

• Enforces least-privilege access
• Standardizes permissions across teams and regions
• Speeds up setup for new projects and campaigns

4. Group-based routing of proofs to the right stakeholders

Data flow: OpenText Directory Services to Ziflow

Directory group membership can be used to determine which users receive proof notifications or are assigned to review stages in Ziflow. For example, proofs for regulated product content can automatically route to legal, compliance, and brand teams based on directory group membership.

• Reduces manual assignment of reviewers
• Improves accountability in approval cycles
• Ensures the right business functions are involved in review

5. Single source of truth for user identity and contact details

Data flow: OpenText Directory Services to Ziflow

User attributes such as name, email address, department, and manager can be synchronized from OpenText Directory Services into Ziflow. This keeps reviewer profiles current and reduces the risk of sending approvals to outdated contacts.

• Improves notification accuracy
• Reduces duplicate user records
• Supports consistent identity data across systems

6. Access control for external agencies and partners

Data flow: Bi-directional, with OpenText Directory Services as the authority for internal users and Ziflow managing external collaboration records

Organizations can use OpenText Directory Services to manage internal employees while Ziflow handles external reviewers from agencies or vendors. Integration can synchronize approved external identities or group memberships so that only authorized partners can participate in proofing workflows.

• Supports secure collaboration with third parties
• Separates internal and external access models
• Helps maintain governance over shared creative assets

7. Audit-ready user and approval governance

Data flow: Bi-directional

Identity events from OpenText Directory Services, such as account creation, role changes, and deactivation, can be correlated with Ziflow approval activity to create a complete audit trail. This is valuable for regulated industries that need to show who had access to content and who approved it at each stage.

• Strengthens auditability and compliance reporting
• Provides traceability between identity and approval actions
• Helps investigate access or workflow issues faster

8. Department-based workspace access for distributed teams

Data flow: OpenText Directory Services to Ziflow

Directory attributes such as department, business unit, or region can be used to automatically place users into the correct Ziflow workspaces or project groups. For example, users in the EMEA marketing directory group can be assigned to the EMEA campaign workspace, while North America teams are routed elsewhere.

• Improves organization of large-scale creative operations
• Supports regional governance and localized workflows
• Reduces administrative effort for workspace management

Overall, integrating OpenText Directory Services with Ziflow helps enterprises centralize identity control while streamlining creative review and approval processes. The result is stronger security, faster onboarding, better workflow routing, and more consistent governance across marketing, legal, and compliance teams.