Confluence - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between Confluence and OpenText TeamSite Authoring Services

1. Publish approved knowledge articles from Confluence to TeamSite-managed web pages

Data flow: Confluence ? OpenText TeamSite Authoring Services

Subject matter experts draft product FAQs, support articles, or policy updates in Confluence, where internal teams collaborate and review content. Once approved, the finalized content is pushed into TeamSite for publication on the corporate website, customer portal, or partner site.

• Reduces duplicate authoring across internal and external channels
• Ensures web content is based on a single approved source
• Speeds up publishing of frequently updated information such as service notices or product guidance

2. Sync marketing campaign briefs and content requirements from TeamSite to Confluence

Data flow: OpenText TeamSite Authoring Services ? Confluence

Marketing teams define campaign pages, landing page requirements, and content requests in TeamSite. Those requirements are automatically mirrored into Confluence spaces for cross-functional collaboration with legal, product, sales, and regional teams.

• Improves visibility into campaign scope and dependencies
• Creates a shared workspace for review comments and approvals
• Helps teams track content readiness before web launch

3. Route web content review and approval tasks through Confluence workflows

Data flow: OpenText TeamSite Authoring Services ? Confluence

When a page or asset is ready for review in TeamSite, an integration creates a Confluence page or task record containing the draft, metadata, and approval checklist. Reviewers use Confluence to capture feedback, decisions, and sign-off notes before the content is returned to TeamSite for final publishing.

• Centralizes review history and approval evidence
• Supports auditability for regulated or brand-sensitive content
• Reduces email-based review cycles and missed approvals

4. Maintain a governed content standards library in Confluence for TeamSite authors

Data flow: Confluence ? OpenText TeamSite Authoring Services

Brand guidelines, tone-of-voice rules, SEO standards, accessibility requirements, and legal disclaimers are maintained in Confluence as the authoritative reference. TeamSite authors access these standards directly while creating or updating web content, helping ensure consistency across all digital properties.

• Improves content quality and compliance
• Reduces rework caused by inconsistent messaging
• Gives distributed authors a single source for publishing rules

5. Link product documentation and release notes in Confluence to customer-facing web content in TeamSite

Data flow: Bi-directional

Product teams document release notes, feature explanations, and implementation guidance in Confluence. Marketing or digital teams then reference those pages when creating customer-facing product pages or release announcement content in TeamSite. Updates in either system can trigger review of the linked content to keep messaging aligned.

• Aligns internal product knowledge with external messaging
• Prevents outdated web copy after product changes
• Supports coordinated launches across product, marketing, and support teams

6. Capture website content change requests in Confluence and push them into TeamSite production queues

Data flow: Confluence ? OpenText TeamSite Authoring Services

Business users submit content change requests in Confluence using a standard template for page updates, new landing pages, or content removals. The integration converts approved requests into TeamSite work items, assigning them to web authors or editors with the required context and attachments.

• Standardizes intake for web content requests
• Improves prioritization and assignment for digital teams
• Provides traceability from request to published change

7. Create a shared knowledge-to-publishing workflow for regional content localization

Data flow: Confluence ? OpenText TeamSite Authoring Services

Global teams maintain master content in Confluence, including source copy, translation notes, and market-specific guidance. Regional digital teams use TeamSite to localize and publish approved variants for country websites, while Confluence stores the source context and decision history.

• Supports controlled localization at scale
• Preserves the intent and rationale behind source content
• Helps regional teams work from approved master materials

8. Track content governance decisions and publishing exceptions across both platforms

Data flow: Bi-directional

When TeamSite content requires exceptions such as legal review, accessibility remediation, or urgent publishing approval, the decision record is captured in Confluence. Confluence then feeds back governance updates, policy changes, or lessons learned to TeamSite authors so future content follows the latest standards.

• Improves governance across web publishing operations
• Creates a durable record of exceptions and approvals
• Helps teams continuously improve content processes