Box - OpenText TeamSite - LiveSite Content Services Integration and Automation

Common Integration Use Cases Between Box and OpenText TeamSite - LiveSite Content Services

1. Secure content repository for website and portal publishing

Data flow: Box ? OpenText TeamSite - LiveSite Content Services

Marketing, legal, and product teams store approved website assets in Box, including images, PDFs, policy documents, and campaign collateral. OpenText TeamSite - LiveSite Content Services pulls the approved content into customer-facing websites and portals for dynamic rendering and publishing.

• Reduces manual file transfers between content owners and web teams
• Ensures only approved, version-controlled assets are published
• Improves governance for regulated content such as disclosures, terms, and compliance documents

2. Controlled review and approval workflow for digital content

Data flow: OpenText TeamSite - LiveSite Content Services ? Box ? OpenText TeamSite - LiveSite Content Services

Content drafts created in TeamSite are exported to Box for legal, compliance, or brand review. Reviewers annotate and approve files in Box, and the final approved version is returned to TeamSite for publication.

• Creates a clear approval trail for audits and compliance
• Supports cross-functional review without exposing publishing systems to broad access
• Speeds up content sign-off for regulated industries and enterprise communications

3. Personalized document delivery from customer portals

Data flow: OpenText TeamSite - LiveSite Content Services ? Box

Customer portals built on TeamSite can generate personalized documents such as account statements, onboarding packets, claims letters, or service summaries and store them in Box for secure access, retention, and sharing with external users.

• Provides a secure, auditable document delivery channel
• Supports customer self-service with controlled access to sensitive files
• Improves retention and lifecycle management of customer-facing documents

4. Centralized asset management for multi-channel digital experiences

Data flow: Box ? OpenText TeamSite - LiveSite Content Services

Teams maintain a single source of truth in Box for brand assets, campaign files, product sheets, and media. TeamSite consumes these assets to publish consistent content across websites, microsites, and partner portals.

• Eliminates duplicate asset storage across departments
• Improves brand consistency across digital channels
• Reduces the risk of outdated or unapproved content being reused

5. Secure external collaboration for web content production

Data flow: OpenText TeamSite - LiveSite Content Services ? Box

Agencies, contractors, and external contributors collaborate on content and creative files in Box, while internal web teams use TeamSite to assemble and publish the final experience. This allows external partners to contribute without direct access to the CMS.

• Limits access to the publishing environment
• Supports secure collaboration with third parties
• Improves turnaround time for campaigns and site updates

6. Compliance archiving of published web content and supporting files

Data flow: OpenText TeamSite - LiveSite Content Services ? Box

When web pages, disclosures, product information, or campaign materials are published, TeamSite sends final content snapshots and supporting documents to Box for retention, legal hold, and audit readiness.

• Creates a defensible archive of what was published and when
• Supports regulatory and legal discovery requirements
• Helps organizations manage content lifecycle policies consistently

7. Content-driven workflow for product launches and regulated updates

Data flow: Box ? OpenText TeamSite - LiveSite Content Services

For product launches, policy updates, or service changes, teams store source documents, approvals, and launch materials in Box while TeamSite manages the customer-facing content experience. Status updates and approved assets move between both systems as the launch progresses.

• Coordinates marketing, compliance, legal, and web operations in one process
• Improves launch speed while maintaining governance
• Provides visibility into content readiness before publication

8. Secure access to supporting documents from dynamic web experiences

Data flow: OpenText TeamSite - LiveSite Content Services ? Box

TeamSite pages can present links or embedded access points to Box-hosted documents such as application forms, policy packets, training materials, or investor documents. Users access the latest controlled version without the web team manually updating files.

• Ensures users always receive the current document version
• Reduces maintenance effort for web administrators
• Supports secure distribution of sensitive content through authenticated portals