Home | Connectors | OpenText DAM (OTMM) | OpenText DAM (OTMM) - SharePoint Integration and Automation
OpenText DAM (OTMM) and SharePoint complement each other well when organizations need a controlled digital asset repository alongside a collaborative workspace for teams, approvals, and business processes. OTMM is best suited for managing rich media assets such as product images, campaign creative, museum collections, and broadcast video, while SharePoint is ideal for collaboration, document workflows, internal portals, and controlled access to business content. The following use cases show how the two platforms can work together in practical enterprise scenarios.
Data flow: OpenText DAM (OTMM) to SharePoint
Marketing teams can store master campaign assets in OTMM, where creative files are versioned, tagged, and approved. Once an asset is finalized, selected renditions, thumbnails, and usage rights metadata can be published to SharePoint campaign sites for regional teams, agencies, and sales users to access.
Data flow: OpenText DAM (OTMM) to SharePoint
Organizations with product information in PIM or ERP systems can use OTMM to manage product photography, pack shots, and lifestyle images. Approved product images can then be synchronized to SharePoint product portals, distributor sites, or internal sales enablement libraries so field teams can quickly find the latest assets.
Data flow: OpenText DAM (OTMM) to SharePoint, with SharePoint to OTMM for feedback and metadata updates
Museums and heritage organizations can store high-resolution collection images and video in OTMM, where preservation metadata and rights information are maintained. Curators, educators, and researchers can use SharePoint team sites to review assets, add comments, manage exhibit planning documents, and coordinate publication schedules. Feedback or metadata corrections can be sent back to OTMM for asset enrichment.
Data flow: OpenText DAM (OTMM) to SharePoint
Photos and videos from company events, conferences, and executive announcements can be ingested into OTMM for tagging, approval, and rights management. Once approved, curated selections can be published to SharePoint news pages, department sites, or leadership portals for internal communications teams to reuse in articles, announcements, and recap pages.
Data flow: Bi-directional
Broadcast teams can manage master video assets, clips, and renditions in OTMM while using SharePoint for production coordination, script approvals, legal review, and scheduling. Editors and producers can access proxy files or links in SharePoint, leave comments, and route documents for approval. Final approved assets can then be pushed back to OTMM for distribution to TV, streaming, or on-demand channels.
Data flow: Bi-directional
Enterprises often need to control how long an image or video can be used, in which markets, and by which teams. OTMM can store rights metadata, expiration dates, and usage restrictions, while SharePoint can surface those rules in team libraries and workflows. If an asset is nearing expiration or has restricted usage, SharePoint workflows can notify stakeholders and trigger review or removal actions.
Data flow: SharePoint to OpenText DAM (OTMM)
Business users can submit asset requests through a SharePoint form or team site, such as requests for a new product image, localized campaign banner, or event video clip. The request can be routed to the DAM team, who then searches OTMM, prepares renditions, and publishes the approved asset back to SharePoint for the requester to access.
Data flow: Bi-directional metadata synchronization
Organizations can synchronize key metadata between OTMM and SharePoint so users can search across both documents and rich media from a single SharePoint experience. For example, a product launch page in SharePoint can surface related images, videos, briefing documents, and approval records from OTMM and SharePoint libraries together.
In summary, OpenText DAM (OTMM) and SharePoint work best together when OTMM serves as the governed media repository and SharePoint acts as the collaboration, workflow, and publishing layer. This combination helps enterprises improve asset control, accelerate content delivery, and support cross-functional teams with a more efficient content operating model.