Agility - OpenText Directory Services Integration and Automation

Common Integration Use Cases Between Agility and OpenText Directory Services

1. Automated user and group provisioning for content editors

Data flow: OpenText Directory Services ? Agility

Synchronize users, roles, and groups from OpenText Directory Services into Agility so marketing, editorial, and web operations teams are automatically provisioned with the correct CMS access. This reduces manual account setup, speeds onboarding, and ensures permissions stay aligned with organizational changes.

Business value: Faster onboarding, fewer access errors, and lower administrative overhead for content operations teams.

2. Role-based access control for regional and departmental content teams

Data flow: Bi-directional, with OpenText Directory Services as the master identity source

Use directory groups to drive Agility permissions for regional marketing teams, business units, or external agencies. For example, a ?North America Marketing? group can be mapped to specific content collections, landing pages, or approval workflows in Agility, while a ?Legal Review? group can be granted read-only access to compliance-sensitive content.

Business value: Better governance, tighter content control, and reduced risk of unauthorized publishing.

3. Automated deprovisioning when employees leave or change roles

Data flow: OpenText Directory Services ? Agility

When a user is disabled, removed from a group, or changes department in OpenText Directory Services, Agility access can be updated automatically. This is especially useful for agencies, contractors, and employees who should lose access immediately when their assignment ends.

Business value: Stronger security posture, reduced compliance risk, and elimination of stale CMS accounts.

4. Single source of truth for editorial and approval workflows

Data flow: OpenText Directory Services ? Agility

Map directory attributes such as department, job title, or location to Agility workflow roles. For example, content created by a local market team can be routed to the correct approvers based on the user?s directory group or organizational unit, ensuring the right stakeholders review content before publication.

Business value: More consistent approvals, fewer workflow bottlenecks, and improved content governance.

5. Centralized identity management for multi-site and headless content operations

Data flow: OpenText Directory Services ? Agility

For organizations running multiple websites, microsites, or headless front ends, use OpenText Directory Services to centrally manage identities across all content teams. Agility can consume these identities to control who can edit specific content models, manage assets, or publish to particular channels.

Business value: Simplified administration across distributed digital properties and consistent access policies across teams.

6. Secure external agency collaboration

Data flow: OpenText Directory Services ? Agility

Provision temporary access for agencies, freelancers, and partners through controlled directory groups. Agility can assign limited permissions for campaign pages, asset uploads, or content review without requiring separate CMS account management for each project.

Business value: Faster collaboration with external teams while maintaining strict access boundaries and auditability.

7. Audit-ready access governance for regulated content environments

Data flow: Bi-directional, with identity and group data originating in OpenText Directory Services

Use OpenText Directory Services as the authoritative identity store and synchronize access assignments into Agility to support audit trails and access reviews. This is valuable for regulated industries where content changes must be traceable to approved users and groups.

Business value: Improved compliance, easier access certification, and stronger accountability for content changes.