OpenText File 360 - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText File 360 and OpenText Core Signature

OpenText File 360 and OpenText Core Signature work well together in document-centric business processes where secure file exchange, controlled collaboration, and legally binding approvals must happen in a single workflow. File 360 provides governed sharing and access control for sensitive documents, while Core Signature adds electronic signing to complete approvals without printing, scanning, or manual handoffs.

1. Secure contract review and signature workflow

Legal, procurement, and sales teams can store draft contracts in OpenText File 360, share them securely with internal reviewers and external counterparties, then route the approved version to OpenText Core Signature for execution.

• Data flow: OpenText File 360 to OpenText Core Signature
• Business value: Faster contract turnaround, fewer versioning errors, and controlled external access
• Typical scenario: Vendor agreements, customer MSAs, NDAs, and renewal documents

2. Employee onboarding document package

HR teams can use OpenText File 360 to distribute onboarding packets such as offer letters, policy acknowledgments, tax forms, and benefit documents. Once the employee reviews the files, selected documents are sent to OpenText Core Signature for signing and return.

• Data flow: OpenText File 360 to OpenText Core Signature, then OpenText Core Signature back to OpenText File 360
• Business value: Shorter onboarding cycles, better auditability, and reduced paper handling
• Typical scenario: New hire acknowledgments, employment agreements, and compliance forms

3. Customer onboarding and account opening approvals

Customer-facing teams can share onboarding documents securely through OpenText File 360, including application forms, disclosures, and supporting documents. After review, OpenText Core Signature captures legally binding signatures and returns the completed package for record retention.

• Data flow: Bi-directional
• Business value: Improved customer experience, faster activation, and stronger compliance controls
• Typical scenario: Financial services account opening, insurance enrollment, and service agreements

4. Controlled external collaboration on regulated documents

Organizations can use OpenText File 360 to collaborate with external advisors, auditors, or partners on sensitive documents while maintaining access controls and audit trails. When final approval is needed, the document is sent to OpenText Core Signature for formal sign-off.

• Data flow: OpenText File 360 to OpenText Core Signature
• Business value: Secure collaboration without email attachments or consumer file-sharing tools
• Typical scenario: Audit responses, compliance attestations, policy approvals, and regulatory submissions

5. Approval routing for policy and governance documents

Business owners can publish draft policies, procedures, and governance documents in OpenText File 360 for review by stakeholders across departments. Once the final version is approved, OpenText Core Signature is used to capture formal sign-off from executives or control owners.

• Data flow: OpenText File 360 to OpenText Core Signature
• Business value: Clear approval records, reduced manual follow-up, and stronger governance
• Typical scenario: Information security policies, HR policy updates, and internal control documentation

6. Supplier onboarding and compliance certification

Procurement teams can share supplier onboarding packets through OpenText File 360, including questionnaires, insurance certificates, and compliance requirements. Suppliers complete and sign required documents in OpenText Core Signature, then the signed files are stored back in File 360 for ongoing access and audit.

• Data flow: Bi-directional
• Business value: Faster supplier setup, better document control, and improved compliance tracking
• Typical scenario: Supplier agreements, code of conduct acknowledgments, and tax documentation

7. Signed document distribution and retention

After a document is executed in OpenText Core Signature, the final signed copy can be automatically stored in OpenText File 360 for secure retention, controlled sharing, and long-term access by authorized teams.

• Data flow: OpenText Core Signature to OpenText File 360
• Business value: Centralized recordkeeping, easier retrieval, and consistent retention practices
• Typical scenario: Executed contracts, signed HR forms, and approved customer documents

Together, OpenText File 360 and OpenText Core Signature create a secure end-to-end document workflow that supports collaboration, approval, execution, and retention with strong governance throughout the process.