OpenText eDOCS - OpenText TeamSite - LiveSite Content Services Integration and Automation

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

1. Publish approved legal content from eDOCS to client-facing portals

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

Legal teams can store final, approved documents in eDOCS and automatically publish selected content to TeamSite-powered portals. This is useful for client advisories, policy updates, regulatory notices, and public-facing legal resources.

• Ensures only version-controlled, approved content is published
• Reduces manual rekeying and duplicate document handling
• Improves speed of publishing time-sensitive legal updates

2. Deliver matter-specific documents through secure client portals

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

Client portals built on TeamSite can surface matter-related documents stored in eDOCS, such as pleadings, contracts, correspondence, or status reports. Access can be personalized by client, matter, or role.

• Provides secure self-service access to relevant documents
• Reduces email-based document sharing and follow-up requests
• Improves client experience with real-time access to current files

3. Sync approved templates and standard clauses for web-based document generation

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

Standard legal templates, clause libraries, and approved forms managed in eDOCS can be exposed through TeamSite for use in web forms or guided document generation workflows. This supports consistent content across internal and external channels.

• Maintains a single source of truth for approved legal language
• Supports faster document creation for business users and clients
• Reduces risk from outdated or non-compliant templates

4. Capture portal-submitted documents into eDOCS for legal review and retention

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

Documents uploaded through TeamSite portals, such as intake forms, signed agreements, evidence files, or supporting records, can be routed into eDOCS for matter-based filing, review, and retention.

• Automates intake from external users into legal repositories
• Supports structured review and approval by legal teams
• Improves compliance with retention and audit requirements

5. Publish legal knowledge articles and FAQs from controlled source documents

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

Legal departments can manage source content in eDOCS and publish selected knowledge articles, FAQs, or policy summaries to TeamSite for employees, clients, or the public. Updates in eDOCS can trigger refreshes on the website or portal.

• Speeds updates to frequently changing legal guidance
• Improves consistency between internal documents and published content
• Reduces content maintenance across multiple channels

6. Support personalized content delivery based on matter, client, or user role

Data flow: Bi-directional

TeamSite can use metadata from eDOCS, such as matter number, client name, document type, or confidentiality level, to personalize what content is shown to each user. In return, user activity in the portal can inform document access patterns and content prioritization.

• Enables context-aware portals for clients and legal staff
• Improves relevance of displayed documents and resources
• Supports role-based access and controlled disclosure

7. Create a unified legal service workflow for intake, publishing, and archival

Data flow: Bi-directional

TeamSite can serve as the front-end for legal service requests, while eDOCS manages the back-end document lifecycle. Requests submitted through the portal can create or update matter records in eDOCS, and approved outputs can be published back to TeamSite for distribution.

• Connects client-facing digital experiences with legal operations
• Improves turnaround time for requests and document delivery
• Provides better governance across creation, approval, publication, and retention