Acquia DAM (Widen) - OpenText Directory Services Integration and Automation

Common Integration Use Cases Between Acquia DAM and OpenText Directory Services

1. Automated user provisioning for DAM access

Data flow: OpenText Directory Services ? Acquia DAM

Synchronize users, groups, and role assignments from OpenText Directory Services into Acquia DAM so marketing teams, agencies, distributors, and retail partners receive the correct access automatically. This reduces manual account setup, prevents permission errors, and ensures users only see the assets and portals relevant to their role or region.

2. Group-based asset portal access control

Data flow: OpenText Directory Services ? Acquia DAM

Use directory groups to control access to Acquia DAM portals and shared collections. For example, a product marketing group can be granted access to launch assets, while a regional sales group receives only localized collateral. This supports tighter governance over brand materials and simplifies access management across distributed teams.

3. Centralized identity management for external collaborators

Data flow: OpenText Directory Services ? Acquia DAM

Manage agency, reseller, and partner identities in OpenText Directory Services and sync them into Acquia DAM for controlled collaboration. External users can be assigned time-bound or project-based access to upload creative files, review approved assets, or download campaign materials without requiring separate account administration in the DAM.

4. Automated deprovisioning when employees change roles or leave

Data flow: OpenText Directory Services ? Acquia DAM

When a user is disabled, moved to a different department, or removed from a group in OpenText Directory Services, their Acquia DAM access is updated automatically. This helps organizations reduce security risk, avoid orphaned accounts, and maintain compliance by ensuring former employees and outdated partners no longer retain access to brand assets.

5. Role-driven workflow participation for asset approvals

Data flow: OpenText Directory Services ? Acquia DAM

Map directory roles to Acquia DAM workflow permissions so only authorized users can submit, review, approve, or publish assets. For example, product managers can approve packaging images, legal reviewers can validate compliance content, and regional marketers can approve localized versions. This improves governance and speeds up asset production cycles.

6. Department and region alignment for localized content distribution

Data flow: OpenText Directory Services ? Acquia DAM

Use organizational attributes from OpenText Directory Services such as department, business unit, or geography to route users into the correct Acquia DAM portals and asset libraries. This is especially useful for global enterprises that need to distribute different product images, language variants, or campaign kits by market while keeping access tightly segmented.

7. Consistent identity data for audit and usage reporting

Data flow: OpenText Directory Services ? Acquia DAM

Synchronize user identity attributes into Acquia DAM so asset usage analytics can be tied back to named users, teams, and business units. Marketing operations can then identify which groups are downloading specific assets, which regions are using approved content most often, and where additional training or content support may be needed.

8. Single source of truth for enterprise access governance

Data flow: Bi-directional governance model, primarily OpenText Directory Services ? Acquia DAM

Establish OpenText Directory Services as the authoritative source for identity and access rules while Acquia DAM consumes those rules for asset access, portal membership, and workflow permissions. This creates a consistent governance model across the enterprise, reduces duplicate identity administration, and supports scalable content operations as the number of users, partners, and assets grows.