OpenText Documentum - Brandfolder Integration and Automation

Common Integration Use Cases Between OpenText Documentum and Brandfolder

OpenText Documentum and Brandfolder serve different but highly complementary purposes. Documentum is optimized for governed, compliant content management and records control, while Brandfolder is built for easy discovery, sharing, and brand-safe use of marketing and product assets. Integrating them helps enterprises balance strict control with fast, self-service access to approved content.

1. Publish approved regulated content from OpenText Documentum to Brandfolder

Direction: OpenText Documentum to Brandfolder

When legal, regulatory, or quality teams approve a document, image, or supporting asset in Documentum, the final approved version can be automatically published to Brandfolder for broader use by marketing, sales, or product teams. This is useful for approved product images, technical diagrams, compliance-approved brochures, and regulated brand materials.

• Reduces manual re-uploading of approved assets
• Ensures only finalized, compliant content reaches Brandfolder
• Improves speed for downstream teams that need ready-to-use assets

2. Sync brand-approved assets from Brandfolder into controlled repositories in OpenText Documentum

Direction: Brandfolder to OpenText Documentum

Marketing teams often create brand assets in Brandfolder first. Once an asset is finalized and marked as approved for enterprise use, it can be pushed into Documentum for long-term retention, governance, or use in regulated workflows. This is valuable for master logos, approved campaign visuals, packaging artwork, and corporate identity files.

• Creates a governed archive of approved brand assets
• Supports retention and audit requirements for enterprise content
• Helps compliance teams maintain a controlled record of externally used assets

3. Use Documentum as the system of record for regulated source content and Brandfolder as the distribution layer

Direction: OpenText Documentum to Brandfolder

In regulated industries, source content such as product claims, safety statements, or approved technical documentation can be stored and controlled in Documentum. Selected versions or derivative assets can then be distributed to Brandfolder for easy access by field teams, partners, or regional marketers. This ensures users work only with sanctioned content.

• Maintains a single governed source of truth
• Prevents use of outdated or non-compliant materials
• Improves access to approved content across distributed teams

4. Trigger review and approval workflows in Documentum for assets prepared in Brandfolder

Direction: Brandfolder to OpenText Documentum

When a marketing team uploads a new asset to Brandfolder, the integration can route it into Documentum for formal review, legal approval, or records classification before release. This is especially useful for product launch materials, claims-based content, and externally distributed collateral that requires compliance sign-off.

• Connects creative production with formal governance
• Supports controlled approval before public release
• Reduces risk of publishing unreviewed content

5. Maintain synchronized metadata for compliance, brand, and campaign governance

Direction: Bi-directional

Metadata such as asset owner, approval status, product line, region, expiration date, and usage rights can be synchronized between Documentum and Brandfolder. Documentum can provide compliance-related metadata, while Brandfolder can provide marketing-oriented tags and campaign context. This makes assets easier to find and safer to use.

• Improves searchability and classification across both systems
• Supports rights management and expiration controls
• Enables consistent reporting on asset status and usage

6. Automate version control for approved assets used across departments

Direction: Bi-directional

When a controlled document or asset is updated in Documentum, the latest approved version can automatically replace the older version in Brandfolder. Likewise, if Brandfolder users identify a new derivative or localized version, it can be sent back to Documentum for formal versioning and retention. This is useful for manuals, product sheets, and branded templates that change frequently.

• Prevents teams from using outdated files
• Reduces duplicate asset management effort
• Supports traceability of version history across systems

7. Support regional or channel-specific asset distribution with governance controls

Direction: OpenText Documentum to Brandfolder

Documentum can store master content and approved variants, while Brandfolder can distribute region-specific or channel-specific versions to local teams, agencies, and partners. For example, a global product image or brochure approved in Documentum can be published to Brandfolder with region tags, language variants, and usage restrictions.

• Enables controlled localization and reuse of approved assets
• Improves consistency across markets and channels
• Reduces the need for local teams to recreate content

8. Retain final campaign assets and evidence of use for audit and records management

Direction: Brandfolder to OpenText Documentum

After a campaign ends, final published assets from Brandfolder can be archived in Documentum along with supporting metadata such as approval records, publication dates, and usage context. This creates a defensible record for audits, legal review, and future reference in regulated environments.

• Supports records retention and audit readiness
• Preserves evidence of what was published and when
• Helps legal and compliance teams respond to inquiries faster

Overall, integrating OpenText Documentum and Brandfolder gives enterprises a practical way to combine strict content governance with fast, user-friendly asset distribution. The result is better compliance, fewer content errors, and more efficient collaboration between regulated content owners and brand-focused teams.