Confluence - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Confluence and OpenText Core Digital Asset Management

1. Centralized Brand and Marketing Asset Library Embedded in Confluence

Data flow: OpenText Core Digital Asset Management to Confluence

Marketing, communications, and product teams can embed approved images, videos, logos, and campaign files stored in OpenText Core Digital Asset Management directly into Confluence pages for briefs, campaign plans, launch checklists, and brand guidelines. This ensures teams always reference the latest approved assets without downloading and reuploading files across documents.

• Reduces use of outdated or unapproved assets
• Improves consistency across campaigns and internal documentation
• Speeds up content creation by making approved assets easy to find and reuse

2. Product Documentation Enriched with Managed Media Assets

Data flow: OpenText Core Digital Asset Management to Confluence

Product and technical documentation teams can pull diagrams, screenshots, training videos, and UI mockups from OpenText Core Digital Asset Management into Confluence pages that describe product features, release notes, implementation guides, and support articles. This keeps documentation visually rich while maintaining control over source files and versions in the asset management system.

• Supports accurate and current documentation
• Improves onboarding and self-service support content
• Creates a single source of truth for media assets used in documentation

3. Campaign Briefs and Creative Reviews Linked to Approved Asset Versions

Data flow: Bi-directional

Teams can use Confluence to manage campaign briefs, review notes, and approval workflows while OpenText Core Digital Asset Management stores the creative files and final approved versions. Confluence pages can link to specific asset records in OpenText Core Digital Asset Management, and asset metadata such as approval status or usage rights can be surfaced back into the brief for review teams.

• Improves collaboration between marketing, legal, and creative teams
• Provides traceability from brief to final asset
• Reduces approval delays by keeping review context and files connected

4. Internal Knowledge Base for Asset Usage Guidelines and Governance

Data flow: OpenText Core Digital Asset Management to Confluence

Organizations can maintain governance content in Confluence, such as asset usage policies, licensing rules, regional restrictions, and brand standards, while linking directly to the relevant assets in OpenText Core Digital Asset Management. This is especially useful for distributed teams that need clear guidance on how and where assets can be used.

• Improves compliance with licensing and brand rules
• Reduces risk of misuse across regions and business units
• Makes governance documentation easier to maintain and distribute

5. Project and Launch Pages with Live Access to Final Deliverables

Data flow: OpenText Core Digital Asset Management to Confluence

For product launches, events, or customer campaigns, project teams can build Confluence launch hubs that include timelines, responsibilities, meeting notes, and direct links to final deliverables stored in OpenText Core Digital Asset Management. This gives stakeholders one place to track the initiative while ensuring the latest approved files are always accessible.

• Improves visibility across cross-functional launch teams
• Reduces time spent searching for final deliverables
• Supports faster execution with fewer handoff errors

6. Training and Enablement Content with Controlled Media Reuse

Data flow: OpenText Core Digital Asset Management to Confluence

Learning and enablement teams can create Confluence-based training materials, onboarding guides, and sales enablement pages that reuse approved screenshots, product videos, and presentation graphics from OpenText Core Digital Asset Management. This allows content owners to update media centrally without manually editing every Confluence page that references it.

• Streamlines onboarding and employee training content maintenance
• Ensures consistent use of approved visuals across materials
• Reduces duplication of effort for content updates

7. Audit-Ready Documentation for Asset Lifecycle and Approvals

Data flow: Bi-directional

Compliance, legal, and operations teams can use Confluence to document approval processes, review checkpoints, and audit procedures while OpenText Core Digital Asset Management provides the authoritative asset history, metadata, and version records. Linking the two systems helps organizations demonstrate who approved an asset, when it was published, and where it is intended to be used.

• Supports audit and compliance requirements
• Improves accountability across content production workflows
• Creates a clear record of asset governance and documentation

8. Cross-Team Content Operations Hub for Requests and Asset Discovery

Data flow: Confluence to OpenText Core Digital Asset Management

Business teams can use Confluence as the front-end workspace for submitting asset requests, documenting requirements, and tracking status, while OpenText Core Digital Asset Management serves as the repository for completed assets. This is effective for organizations that want a simple request intake and collaboration layer without exposing the complexity of the DAM to all users.

• Improves intake and coordination for creative services teams
• Provides a structured process for requesting and delivering assets
• Helps non-technical users work through a familiar collaboration interface