This guide provides technical instructions for the final validation, security configuration, and secure dispatch of an envelope to its designated recipients.
Prerequisites
- Successful completion of asset ingestion and recipient assignment.
- Finalized placement of all mandatory cryptographic fields.
- Assigned role with permission to initiate document transactions.
Strategic Overview
The Send operation is the point of no return in the document lifecycle. It triggers the final cryptographic locking of the envelope metadata and the initialization of the secure notification sequence. During this phase, IUSign generates unique, time-bound access tokens for each recipient and prepares the audit repository for real-time engagement tracking. A successful dispatch is the culmination of the orchestration phase and the beginning of the execution phase.
Implementation Sequence
1. Pre-Dispatch Validation (The "Review" Gate)
Before dispatch, utilize the Review Interface to perform a final audit of the transaction:
- Recipient Verification: Ensure email addresses are syntactically correct and assigned to the proper roles.
- Field Completeness: The platform will automatically flag any documents that lack mandatory signature fields for any assigned recipient.
- Sequencing Check: Confirm that the routing order (Sequential or Parallel) aligns with organizational approval workflows.
2. Advanced Security Configuration
Configure optional security parameters to enhance the defensibility of the transaction:
- Access Authentication: Enable an additional layer of security (e.g., SMS-based 2FA or Access Code) that the recipient must satisfy before viewing the document.
- Temporal Expiry: Define a specific expiration date (e.g., 30 days) after which the envelope will be automatically voided if not completed.
- Notification Frequency: Set the interval for automated reminders (e.g., "Remind every 3 days") to maintain workflow momentum.
3. Execution of Dispatch
Select the Send Envelope action. The IUSign engine then executes the following background operations:
- Token Synthesis: Generation of unique, high-entropy signing tokens for each recipient.
- Immutable Logging: Recording of the
ENVELOPE_SENTevent in the audit trail, including the initiator's IP and User Agent. - SMTP Orchestration: Dispatch of the cryptographically signed email invitations via IUSign's high-deliverability mail infrastructure.
Strategic Considerations: Dispatch Management
- Custom Branding: For Growth and Enterprise tiers, ensure your White-Label Settings are active. This ensures the invitation email utilizes your corporate domain and logo, maximizing recipient trust.
- Private Messages: You may append a personalized message to the invitation. This is highly recommended for high-value transactions to provide context and urgency.
- Recipient Visibility: If the envelope contains multiple documents, verify that the Recipient Visibility settings correctly restrict or grant access to the appropriate assets for each participant.
Forensic Logging and Metadata
Every dispatch event is recorded with the following forensic telemetry:
- Dispatch ID: A unique UUID linking the SMTP event to the envelope.
- Recipients Manifest: A snapshot of all participants and their assigned roles at the moment of sending.
- System Integrity Hash: A hash of the entire envelope state, ensuring no post-dispatch modification can occur without detection.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Dispatch blocked | Missing mandatory fields | Review all documents in the packet and ensure every "Signer" has at least one signature field assigned. |
| Email delivery failure | Invalid address or SMTP block | Verify recipient email syntax. If valid, consult the Email Deliverability Guide. |
| Token generation error | System-level latency | Wait 60 seconds and re-attempt. If the error persists, contact Technical Support. |