Box - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between Box and OpenText Core Signature

1. Contract approval and signature workflow for sales and procurement

Teams store draft agreements in Box, route them for internal review, and then send the approved version to OpenText Core Signature for legally binding signatures. Once fully executed, the signed copy is automatically returned to Box for secure storage, version control, and retention management.

• Data flow: Box to OpenText Core Signature, then OpenText Core Signature back to Box
• Business value: Shortens contract cycle times, reduces manual handoffs, and creates a single governed repository for final executed documents

2. HR onboarding documents and employment agreements

HR teams can prepare offer letters, policy acknowledgements, and employment agreements in Box, then trigger signature requests through OpenText Core Signature. After completion, signed documents are stored in the employee onboarding folder in Box for audit readiness and long term retention.

• Data flow: Box to OpenText Core Signature to Box
• Business value: Improves onboarding speed, reduces paper based processing, and ensures employee records are centrally managed and compliant

3. Customer onboarding and account opening packages

Financial services, insurance, and SaaS organizations can use Box to assemble onboarding packets such as application forms, disclosures, and consent documents. OpenText Core Signature handles the signature step, and the completed package is returned to Box to support downstream onboarding, compliance review, and customer service access.

• Data flow: Box to OpenText Core Signature to Box
• Business value: Creates a faster customer onboarding experience while preserving secure document handling and traceability

4. Legal and compliance review with controlled signature release

Legal teams can manage redlines, supporting evidence, and approval documents in Box, then release only the final approved version to OpenText Core Signature. This prevents premature signing of unapproved content and ensures the signed record is archived in Box with the correct metadata and retention policy.

• Data flow: Box to OpenText Core Signature to Box
• Business value: Strengthens document governance, reduces signing errors, and supports audit and regulatory requirements

5. Vendor onboarding and master service agreement execution

Procurement teams can maintain vendor questionnaires, insurance certificates, and agreement drafts in Box, then send the final contract to OpenText Core Signature for execution by the supplier. After signature, Box becomes the system of record for the signed agreement and related onboarding artifacts.

• Data flow: Box to OpenText Core Signature to Box
• Business value: Speeds supplier activation, improves visibility into onboarding status, and centralizes vendor documentation

6. Policy acknowledgement and annual compliance attestations

Organizations can distribute policy documents from Box to employees or contractors, collect signatures or acknowledgements in OpenText Core Signature, and then store completed attestations back in Box. This is useful for annual code of conduct acknowledgements, security training confirmations, and regulatory attestations.

• Data flow: Box to OpenText Core Signature to Box
• Business value: Simplifies compliance tracking, improves completion rates, and creates a searchable archive of acknowledgements

7. Bi directional status tracking for document lifecycle management

Box can act as the content hub while OpenText Core Signature provides signature status updates such as sent, viewed, signed, declined, or expired. These updates can be written back to Box metadata or workflow states so business users can monitor document progress without leaving Box.

• Data flow: OpenText Core Signature to Box
• Business value: Gives teams real time visibility into signature progress, reduces follow up emails, and supports workflow automation

8. Secure retention of executed documents with governance controls

After a document is signed in OpenText Core Signature, the final executed copy can be automatically stored in Box with retention labels, access permissions, and legal hold policies applied. This is especially valuable for regulated records such as contracts, HR files, and customer consent forms.

• Data flow: OpenText Core Signature to Box
• Business value: Ensures signed records are preserved securely, supports compliance obligations, and reduces the risk of lost or unmanaged documents