OpenText TeamSite Authoring Services - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between OpenText TeamSite Authoring Services and OpenText Core Digital Asset Management

OpenText TeamSite Authoring Services and OpenText Core Digital Asset Management work well together in enterprise content operations. TeamSite manages structured web content creation, review, and publishing, while Core Digital Asset Management centralizes approved images, videos, documents, and brand assets. Integrating them helps marketing, web, and brand teams reuse approved assets, reduce manual handling, and keep digital experiences consistent.

1. Insert approved brand assets directly into web content

Data flow: OpenText Core Digital Asset Management to OpenText TeamSite Authoring Services

Content authors can search and insert approved images, videos, and documents from Core Digital Asset Management directly into TeamSite pages and components without downloading files locally. This ensures only current, approved assets are used in web content and reduces the risk of outdated or unlicensed media being published.

Business value: Faster page creation, stronger brand consistency, and lower compliance risk.

2. Sync published web content previews back to the asset repository

Data flow: OpenText TeamSite Authoring Services to OpenText Core Digital Asset Management

When a page, campaign landing page, or content module is approved in TeamSite, a rendered preview or final published snapshot can be stored in Core Digital Asset Management as a reference asset. Brand, legal, and regional teams can then review how assets are used in context and maintain an audit trail of approved executions.

Business value: Better governance, easier auditability, and improved reuse of approved content examples.

3. Automate asset metadata transfer into content workflows

Data flow: OpenText Core Digital Asset Management to OpenText TeamSite Authoring Services

Asset metadata such as campaign name, product line, region, usage rights, expiration date, and language can be passed into TeamSite when an asset is selected. Authors can use this metadata to populate page fields, route content through the right approval path, and prevent use of assets outside their approved territory or time window.

Business value: Less manual data entry, fewer publishing errors, and stronger rights management.

4. Trigger content updates when assets are replaced or expire

Data flow: OpenText Core Digital Asset Management to OpenText TeamSite Authoring Services

If a key image, video, or document is updated, replaced, or marked expired in Core Digital Asset Management, TeamSite can flag all pages using that asset for review. Content owners can then update affected pages before outdated or non-compliant assets remain live on the website.

Business value: Reduced content risk, faster remediation of expired assets, and improved governance across digital properties.

5. Launch campaign content from a shared asset package

Data flow: Bi-directional

Marketing teams can assemble a campaign package in Core Digital Asset Management containing approved creative, product photography, logos, and supporting documents. TeamSite then uses that package to build landing pages, banners, and promotional modules. As campaign assets are refined or localized, updates can flow back to the asset repository for reuse across channels.

Business value: Faster campaign launch, consistent cross-channel execution, and better asset reuse.

6. Support localization and regional content adaptation

Data flow: OpenText Core Digital Asset Management to OpenText TeamSite Authoring Services

Regional teams can pull localized asset variants from Core Digital Asset Management into TeamSite based on language, market, or brand rules. For example, a global product image can have region-specific overlays, translated brochures, or market-approved videos that are automatically available to the correct TeamSite workflow.

Business value: Efficient localization, reduced duplication, and improved regional compliance.

7. Maintain a single source of truth for approved digital assets

Data flow: Bi-directional, with Core Digital Asset Management as the master repository

Core Digital Asset Management serves as the authoritative source for approved media, while TeamSite references those assets in web content rather than storing separate copies. Usage information from TeamSite can be sent back to the DAM to show where assets are deployed, which supports governance, reporting, and lifecycle management.

Business value: Lower storage duplication, clearer asset ownership, and better visibility into asset usage across the enterprise.

8. Improve approval workflows for regulated content

Data flow: Bi-directional

For regulated industries such as healthcare, financial services, or manufacturing, assets can be approved in Core Digital Asset Management before being made available in TeamSite. TeamSite then routes page content through editorial, legal, and compliance review using the approved asset set. If an asset is rejected or withdrawn in the DAM, TeamSite can automatically remove it from pending content workflows.

Business value: Stronger compliance controls, fewer publishing delays, and reduced risk of unauthorized content use.