SharePoint - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between SharePoint and OpenText Core Signature

1. Contract approval and signature workflow from SharePoint document libraries to OpenText Core Signature

Legal, procurement, and sales teams store draft contracts in SharePoint, where version control, metadata, and internal review are managed. Once a document reaches the approval stage, SharePoint automatically sends the final version to OpenText Core Signature for legally binding signatures. After completion, the signed copy is returned to SharePoint and stored in the correct library with the final status, audit trail, and retention tags.

Business value: Reduces manual email-based approvals, ensures a single controlled contract repository, and improves turnaround time for signature execution.

Data flow: SharePoint to OpenText Core Signature, then OpenText Core Signature back to SharePoint.

2. HR onboarding packet signing with signed records archived in SharePoint

HR teams prepare onboarding documents such as offer letters, policy acknowledgements, and tax forms in SharePoint. New hires receive signature requests through OpenText Core Signature, complete them electronically, and the signed documents are automatically archived in the employee onboarding site or HR records library in SharePoint. HR can track completion status in SharePoint and follow up on outstanding items.

Business value: Speeds up onboarding, reduces paper handling, and creates a centralized employee record for compliance and audit readiness.

Data flow: SharePoint to OpenText Core Signature, with status and completed documents returned to SharePoint.

3. Customer onboarding and account setup documents routed from SharePoint to OpenText Core Signature

Operations or customer success teams maintain onboarding checklists and supporting documents in SharePoint, including service agreements, consent forms, and account setup paperwork. When a customer packet is ready, SharePoint triggers OpenText Core Signature to collect signatures from customers and internal approvers. Once signed, the completed package is stored back in SharePoint and linked to the customer record or project site.

Business value: Shortens customer onboarding cycles, improves visibility across teams, and ensures signed documents are retained with the related case or account file.

Data flow: SharePoint to OpenText Core Signature, then OpenText Core Signature back to SharePoint.

4. Policy acknowledgement and compliance attestation workflow

Compliance and HR teams publish updated policies in SharePoint, such as code of conduct, security policies, or regulatory acknowledgements. Employees are assigned signature tasks through OpenText Core Signature to confirm review and acceptance. Signed acknowledgements are automatically stored in SharePoint, where managers and compliance officers can report on completion rates and maintain evidence for audits.

Business value: Improves policy compliance, provides defensible audit records, and reduces the administrative burden of tracking acknowledgements manually.

Data flow: SharePoint to OpenText Core Signature, with completion records and signed acknowledgements returned to SharePoint.

5. Vendor and procurement agreement execution with controlled document governance

Procurement teams manage vendor agreements, statements of work, and purchase-related documents in SharePoint. After internal review and approval, the agreement is routed to OpenText Core Signature for external vendor signatures. Signed documents are then returned to SharePoint, where they are stored alongside supporting procurement records, approval history, and related correspondence.

Business value: Creates a controlled end-to-end procurement workflow, improves contract visibility, and supports stronger governance over supplier commitments.

Data flow: SharePoint to OpenText Core Signature, then OpenText Core Signature back to SharePoint.

6. Board and executive approval packages with secure signature capture

Executive assistants and governance teams assemble board packs, resolutions, and approval memos in SharePoint. When formal approval is required, selected documents are sent to OpenText Core Signature for signatures from board members or executives. After execution, the signed documents are returned to SharePoint and stored in restricted-access libraries with version history and retention controls.

Business value: Supports secure governance processes, reduces delays in executive approvals, and keeps sensitive records centralized and protected.

Data flow: SharePoint to OpenText Core Signature, then OpenText Core Signature back to SharePoint.

7. Bi-directional status tracking for signature requests and document lifecycle management

SharePoint can act as the operational workspace for document preparation and tracking, while OpenText Core Signature manages the signing event and status updates. Signature progress, completion timestamps, and signer responses can be synchronized back to SharePoint so business users can monitor document lifecycle status without leaving the collaboration site. This is especially useful for teams managing high volumes of approvals across departments.

Business value: Improves transparency, reduces follow-up effort, and gives teams a single place to monitor document progress from draft to signed completion.

Data flow: Bi-directional between SharePoint and OpenText Core Signature.