OpenText TeamSite - LiveSite Content Services - Sanity Integration and Automation

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

1. Centralized structured content authoring with dynamic delivery to customer portals

Data flow: Sanity → OpenText TeamSite - LiveSite Content Services

Marketing and product teams create reusable structured content in Sanity, such as banners, product highlights, FAQs, and campaign messages. OpenText TeamSite - LiveSite Content Services consumes that content and renders it dynamically across websites and portals with personalization rules based on customer segment, location, or behavior.

• Reduces duplicate content entry across channels
• Improves speed of campaign launches
• Ensures consistent content across web experiences

2. Personalized content assembly using customer and context data

Data flow: Bi-directional

OpenText TeamSite - LiveSite Content Services uses real-time customer context from backend systems to determine which content variant to display, while Sanity stores the approved content blocks and variants. This supports personalized landing pages, account dashboards, and service pages tailored to customer profile, lifecycle stage, or entitlement.

• Enables context-aware digital experiences
• Supports targeted messaging without hardcoding pages
• Improves conversion and self-service adoption

3. Editorial workflow for reusable content with enterprise publishing controls

Data flow: Sanity → OpenText TeamSite - LiveSite Content Services

Content teams manage reusable assets and structured page components in Sanity, then publish approved content to OpenText TeamSite - LiveSite Content Services for controlled delivery. OpenText can enforce channel-specific presentation, approval gates, and publishing schedules for regulated or high-visibility content.

• Separates content creation from presentation
• Supports governance for regulated industries
• Improves collaboration between editors, legal, and web operations

4. Omnichannel content syndication for web, portal, and mobile experiences

Data flow: Sanity → OpenText TeamSite - LiveSite Content Services

Sanity acts as the master repository for structured content that must be reused across multiple digital touchpoints. OpenText TeamSite - LiveSite Content Services consumes the same content for customer portals, authenticated web experiences, and campaign microsites, ensuring consistent messaging while allowing channel-specific rendering.

• Eliminates content silos across channels
• Speeds rollout of new digital properties
• Supports a single source of truth for reusable content

5. Content enrichment from digital asset and backend systems

Data flow: Bi-directional

Sanity stores structured content references, while OpenText TeamSite - LiveSite Content Services pulls in live data from backend systems such as CRM, pricing, or product catalogs to enrich the experience at render time. This is useful for pages that need both editorial content and real-time operational data, such as service status pages, product detail pages, or account-specific offers.

• Combines editorial control with live business data
• Reduces stale content on customer-facing pages
• Improves accuracy for pricing, availability, and service information

6. Rapid campaign updates with governed publishing to production

Data flow: Sanity → OpenText TeamSite - LiveSite Content Services

Campaign teams use Sanity to quickly update headlines, offers, and promotional modules during active campaigns. OpenText TeamSite - LiveSite Content Services then publishes those updates to production with enterprise controls, allowing fast changes without requiring front-end code releases.

• Shortens campaign change turnaround time
• Reduces dependency on development teams
• Supports time-sensitive promotions and announcements

7. Content migration and modernization of legacy web experiences

Data flow: OpenText TeamSite - LiveSite Content Services → Sanity

Organizations modernizing their digital experience stack can migrate reusable content from OpenText TeamSite - LiveSite Content Services into Sanity to support more flexible content modeling and faster authoring. This is especially useful when moving toward headless or composable architecture while preserving existing content investments.

• Supports phased modernization without a full rebuild
• Improves content reuse and editorial agility
• Helps decouple content from legacy page structures

8. Cross-team governance for content lifecycle and approval

Data flow: Bi-directional

Sanity manages draft creation and collaborative editing, while OpenText TeamSite - LiveSite Content Services handles final publication and delivery governance. This creates a clear workflow for content, legal, compliance, and web operations teams, especially for industries that require review, auditability, and controlled release processes.

• Improves accountability across content lifecycle stages
• Supports audit-ready publishing processes
• Reduces risk of unauthorized or inconsistent content release