OpenText Directory Services - NetX Integration and Automation

Common Integration Use Cases Between OpenText Directory Services and NetX

OpenText Directory Services provides centralized identity and group management, while NetX is typically used as a digital asset management platform for storing, organizing, and distributing approved media and brand content. Integrating the two helps enterprises control access, streamline user provisioning, and align content permissions with corporate identity governance.

1. Automated user provisioning for NetX from OpenText Directory Services

Data flow: OpenText Directory Services to NetX

When employees, contractors, or agency users are created or updated in OpenText Directory Services, their accounts can be automatically provisioned in NetX with the correct profile, department, and access level. This reduces manual account setup for marketing, communications, and creative operations teams.

• New users are added to NetX based on directory attributes
• Role changes in the directory update NetX permissions automatically
• Inactive users can be disabled in NetX when removed from the directory

2. Group-based access control for brand and asset libraries

Data flow: OpenText Directory Services to NetX

Directory groups can be mapped to NetX collections, folders, or asset libraries so that access is granted based on business role rather than individual user management. This is especially useful for separating internal teams, regional offices, agencies, and external partners.

• Marketing groups access campaign assets
• Legal or compliance groups access approved master files
• Regional teams see only assets relevant to their market

3. Single sign-on for secure access to NetX

Data flow: OpenText Directory Services to NetX

Users authenticate once through the enterprise directory and then access NetX without separate credentials. This improves user experience and reduces password-related support requests while maintaining centralized identity control.

• Employees use corporate credentials to log in to NetX
• Authentication policies remain governed by the directory team
• Access can be revoked centrally when employment status changes

4. Automated deprovisioning of NetX access when users leave the organization

Data flow: OpenText Directory Services to NetX

When a user account is disabled or removed in OpenText Directory Services, NetX access can be automatically suspended or removed. This helps reduce security risk and ensures former employees or vendors no longer retain access to sensitive content.

• Immediate access removal for terminated users
• Reduced audit findings related to orphaned accounts
• Lower administrative burden for IT and security teams

5. Attribute-driven personalization of NetX access and workspace assignment

Data flow: OpenText Directory Services to NetX

User attributes such as department, location, job title, or business unit can be used to assign NetX workspaces, default folders, or content views. This helps users land directly in the right environment without manual setup.

• Sales users see sales enablement assets
• Product teams see launch materials and technical media
• Country-specific users are routed to localized content libraries

6. External partner access governed by directory-managed identities

Data flow: OpenText Directory Services to NetX

Agencies, freelancers, and distributors can be managed as controlled identities in OpenText Directory Services and granted limited NetX access based on project or contract scope. This supports secure collaboration without creating unmanaged local accounts in NetX.

• Time-bound access for campaign agencies
• Restricted access to approved asset sets only
• Consistent offboarding when partner engagement ends

7. Centralized audit and compliance support for content access

Data flow: Bi-directional, with OpenText Directory Services providing identity context and NetX providing access activity

Identity data from OpenText Directory Services can be combined with NetX usage logs to support audit reporting, access reviews, and compliance investigations. This gives security and governance teams a clearer view of who accessed which assets and under what role.

• Trace asset access back to authenticated users and groups
• Support periodic access certification reviews
• Improve evidence collection for regulatory or brand compliance audits

8. Role-based workflow routing for content approval and publishing

Data flow: OpenText Directory Services to NetX

Directory roles can be used to route content approval tasks in NetX to the correct reviewers, such as legal, brand, regional marketing, or product management. This shortens approval cycles and ensures the right stakeholders review content before publication.

• Legal reviewers assigned automatically based on role
• Regional approvers receive localized content for sign-off
• Publishing rights limited to approved business roles

Overall, integrating OpenText Directory Services with NetX helps enterprises strengthen access governance, reduce manual administration, and make digital asset operations more secure and efficient.