OpenText DAM (OTMM) - OpenText Directory Services Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and OpenText Directory Services

OpenText DAM (OTMM) manages rich media assets such as product images, videos, campaign content, museum collections, and broadcast media, while OpenText Directory Services provides centralized user, group, and access management. Together, they support secure, role-based collaboration across marketing, product, creative, and operations teams.

1. Automated User Provisioning for DAM Access

When a new employee, contractor, or agency user is added in OpenText Directory Services, their account and group memberships can be synchronized to OpenText DAM (OTMM) to grant the correct access level automatically.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Faster onboarding, fewer manual access requests, and reduced risk of unauthorized asset access.

• Example: A new brand manager is added to the marketing group and immediately receives access to campaign folders, approved product imagery, and download permissions.

2. Role-Based Asset Access for Internal and External Teams

Directory groups can be mapped to DAM roles so that users only see the collections and functions relevant to their job, such as editors, approvers, distributors, or archivists.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Stronger governance, simpler permission management, and better separation of duties.

• Example: Creative agencies are assigned upload-only access to campaign workspaces, while legal reviewers receive read and approve rights for final assets.

3. Centralized Offboarding and Access Revocation

When a user is disabled or removed from a group in OpenText Directory Services, their access to OpenText DAM (OTMM) is automatically revoked, including access to sensitive product launches, embargoed media, or restricted museum collections.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Reduces security exposure and ensures immediate compliance with access policies.

• Example: A departing contractor loses access to all campaign assets and distribution folders on their last day without manual intervention.

4. Department and Region Based Content Segmentation

Directory attributes such as department, location, or business unit can be used to control which DAM collections users can access, helping organizations manage regional product catalogs, localized marketing content, or museum collection subsets.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Better content governance and easier management of distributed teams across regions or brands.

• Example: European marketing teams access only EU-approved product images and localized video assets, while North American teams see their own regional content library.

5. Approval Workflow Routing Based on User Identity

OpenText Directory Services can provide user identity and group information to OpenText DAM (OTMM) so that asset approval workflows route automatically to the correct reviewers based on role, team, or business unit.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Faster approvals, fewer workflow errors, and improved accountability.

• Example: Product images submitted for publication are routed to the product owner, brand approver, and legal reviewer based on their directory group memberships.

6. Secure Access for External Agencies and Partners

External users managed in OpenText Directory Services can be granted time-bound access to specific DAM collections for campaign execution, media review, or content delivery without exposing the full asset repository.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Enables controlled collaboration with agencies, distributors, and production partners.

• Example: A video production agency receives access only to a broadcast project folder for the duration of the campaign, then access is removed automatically.

7. Audit and Compliance Reporting by User Identity

User and group identities from OpenText Directory Services can be linked to DAM activity logs to support audit reporting, showing who accessed, approved, downloaded, or distributed specific assets.

• Data flow: Bi-directional, with OpenText Directory Services providing identity context to OpenText DAM (OTMM) and OpenText DAM (OTMM) returning usage events for reporting

• Business value: Stronger compliance, better traceability, and easier investigation of content misuse.

• Example: A museum can trace which curator or external researcher accessed a restricted digital collection item and when.

8. Single Sign-On and Consistent User Experience Across OpenText Tools

By using OpenText Directory Services as the central identity store, users can authenticate once and access OpenText DAM (OTMM) with consistent permissions, reducing login friction and support calls.

• Data flow: OpenText Directory Services to OpenText DAM (OTMM)

• Business value: Improved productivity, fewer password issues, and a more seamless enterprise user experience.

• Example: A marketing team member signs in once and can move between asset search, review, and download tasks without repeated authentication prompts.