Box - OpenText Core Digital Asset Management Integration and Automation

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

1. Centralized Brand Asset Distribution from OpenText Core Digital Asset Management to Box

Marketing and creative teams can store approved master assets such as logos, product images, campaign videos, and brand templates in OpenText Core Digital Asset Management, then automatically publish selected files to Box for broader internal access by sales, regional teams, agencies, and partners. This gives business users a secure collaboration space in Box while keeping the authoritative asset library governed in OpenText Core Digital Asset Management.

• Data flow: OpenText Core Digital Asset Management to Box
• Business value: Faster asset access without exposing the full master library
• Typical users: Marketing, sales enablement, external agencies

2. Approved Content Intake from Box into OpenText Core Digital Asset Management

Teams can use Box as the working area for draft content, then move final approved files into OpenText Core Digital Asset Management for long-term asset management, tagging, and reuse. For example, a product launch team may collaborate in Box on campaign drafts, and once approved, the final images and videos are transferred into OpenText Core Digital Asset Management with metadata for future campaigns.

• Data flow: Box to OpenText Core Digital Asset Management
• Business value: Reduces duplicate storage and ensures only approved assets enter the DAM
• Typical users: Creative operations, brand governance, content managers

3. Secure External Review and Approval Workflow

OpenText Core Digital Asset Management can provide the controlled source of creative assets, while Box can be used to share review packages with internal stakeholders or external reviewers who need secure access, comments, and version tracking. Once feedback is complete, the revised asset can be returned to OpenText Core Digital Asset Management for final approval and publication.

• Data flow: Bi-directional
• Business value: Streamlines review cycles and maintains a clear approved version history
• Typical users: Legal, compliance, marketing, agencies

4. Campaign Asset Handoff to Regional Teams

Global marketing teams can manage master campaign assets in OpenText Core Digital Asset Management and push localized or region-specific versions into Box folders for country teams to access and deploy. Regional teams can then add local documents, translations, and execution materials in Box without affecting the master asset repository.

• Data flow: OpenText Core Digital Asset Management to Box
• Business value: Supports localization while preserving brand consistency
• Typical users: Global marketing, regional marketing, field teams

5. Box as a Collaboration Layer for Asset Requests and Intake

Business users can submit creative requests, reference files, and supporting documents in Box, where project teams collaborate on requirements before assets are created or selected in OpenText Core Digital Asset Management. Once the request is finalized, the resulting approved asset can be stored in OpenText Core Digital Asset Management and linked back to the Box request record for traceability.

• Data flow: Box to OpenText Core Digital Asset Management, with reference links back to Box
• Business value: Improves request intake and creates a clear audit trail from brief to final asset
• Typical users: Marketing operations, creative services, business stakeholders

6. Rights and Compliance Controlled Asset Sharing

OpenText Core Digital Asset Management can manage usage rights, expiration dates, and approved distribution status for digital assets, while Box can be used to share only the assets that are cleared for a specific audience or time period. When an asset expires or loses usage rights, the integration can automatically remove or restrict access in Box to reduce compliance risk.

• Data flow: OpenText Core Digital Asset Management to Box
• Business value: Lowers legal and brand risk by enforcing asset usage rules
• Typical users: Legal, compliance, brand governance, marketing operations

7. Asset Metadata Synchronization for Better Search and Reuse

When assets move between the two platforms, key metadata such as campaign name, product line, region, rights status, and approval state can be synchronized so users can search and filter consistently in both systems. This helps teams find the right file faster and reduces the chance of using outdated or unapproved content.

• Data flow: Bi-directional
• Business value: Improves discoverability and reduces duplicate asset creation
• Typical users: Content operations, marketing, sales enablement

8. Long-Term Archive and Governance of Final Assets

After a campaign ends, final approved assets can be moved from Box into OpenText Core Digital Asset Management for structured archiving, while Box retains only active working files. This keeps Box focused on collaboration and OpenText Core Digital Asset Management focused on governed asset lifecycle management, retention, and reuse.

• Data flow: Box to OpenText Core Digital Asset Management
• Business value: Reduces clutter in collaboration spaces and strengthens content governance
• Typical users: Records management, marketing operations, compliance teams