OpenText Core Signature - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between OpenText Core Signature and OpenText TeamSite Authoring Services

• Digital approval of website content before publishing
  Marketing teams draft or update web pages in OpenText TeamSite Authoring Services, then route the final content package to OpenText Core Signature for legally binding approval by legal, compliance, or brand stakeholders. Once signed, the approved content is released for publication. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature.
• Consent capture for customer-facing web forms
  TeamSite hosts customer onboarding, registration, or lead capture pages that require explicit consent or terms acceptance. After form submission, OpenText Core Signature captures the electronic signature and returns the signed consent record to TeamSite or a connected repository for audit and retention. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature, then back to TeamSite.
• Policy and compliance acknowledgment for intranet content
  HR or internal communications teams publish policy updates, employee handbooks, or mandatory notices in TeamSite. Employees are prompted to sign acknowledgment forms through Core Signature, and the signed acknowledgments are linked back to the original content record for tracking and audit. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature, with status returned to TeamSite.
• Approval workflow for regulated marketing campaigns
  For industries such as financial services or healthcare, campaign assets and landing page copy created in TeamSite can be routed to Core Signature for approval by compliance officers, legal reviewers, and product owners before the campaign goes live. This reduces launch delays and creates a defensible approval trail. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature.
• Signed release authorization for externally published content
  When a high-risk webpage, press release, or investor communication requires formal sign-off, TeamSite sends the final version to Core Signature for authorized approval. The signed document is then stored with the content record, ensuring the published version matches the approved version. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature, with signed output returned to TeamSite or ECM.
• Documented approval of multilingual content variants
  Global marketing teams manage localized page versions in TeamSite and need region-specific approvals before publishing. Core Signature captures approval from local legal, regulatory, or marketing approvers for each language or market variant, helping ensure regional compliance. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature.
• Audit-ready retention of signed content approvals
  TeamSite manages the content lifecycle, while Core Signature provides the signed approval artifact. The signed approval, signer identity, timestamps, and content version are linked to the content record so auditors can verify who approved what and when. Data flow: Bi-directional between OpenText TeamSite Authoring Services and OpenText Core Signature.
• Controlled publishing for partner or franchise portals
  Corporate teams create standardized portal content in TeamSite for partners, dealers, or franchisees. Before publishing changes that affect contractual terms, pricing disclosures, or brand statements, Core Signature is used to obtain formal approval from business owners and legal teams. Data flow: OpenText TeamSite Authoring Services to OpenText Core Signature.