This guide provides technical instructions for the definition, sequencing, and role assignment of participants within an IUSign document workflow.
Prerequisites
- Successful initialization of an envelope and asset ingestion.
- Verified email identities for all participants.
Strategic Overview
Recipients are the active participants in a document lifecycle. IUSign's orchestration engine allows for the definition of complex routing paths, ranging from simple parallel signing to multi-stage sequential approvals. Assigning the correct Role and Routing Order is essential for ensuring that the document moves through the organizational hierarchy in a compliant and efficient manner. Every recipient's identity is cryptographically bound to the transaction, forming the basis of the final non-repudiation proof.
Implementation Sequence
1. Recipient Identity Specification
Add participants by specifying their primary identity parameters:
- Legal Name: Required for forensic identification.
- Email Address: The primary delivery vector for the secure signing invitation.
2. Role Assignment and Authority
Define the operational authority for each participant:
| Role Category | Functional Description | Use Case |
|---|---|---|
| Needs to Sign | Mandatory cryptographic execution required. | Signatories, Approvers. |
| Receives a Copy (CC) | Read-only access upon completion. | Legal Dept, Stakeholders. |
| Needs to View | Mandatory opening of the document required. | Formal disclosure review. |
3. Routing Order Orchestration
IUSign supports two primary routing modes:
- Sequential Routing (1 → 2 → 3): The document is dispatched to recipients in a specific numerical order. Recipient 2 only receives the invitation once Recipient 1 has successfully executed their requirements.
- Parallel Routing (1, 1, 1): The document is dispatched to all recipients simultaneously. Any participant can sign at any time.
[!TIP] Use Sequential Routing for workflows requiring hierarchical approval (e.g., Manager signs only after Employee). Use Parallel Routing for multi-party agreements where the order of signature is irrelevant.
4. Advanced Security Configuration
For high-sensitivity transactions, enable additional identity verification layers:
- Access Code: A shared secret defined by the sender.
- SMS Authentication (Growth+): Two-factor verification via the recipient's mobile device.
Technical Specifications: Recipient Manifest
| Parameter | Specification | Functional Impact |
|---|---|---|
| Max Recipients | 10 (Standard) / 100 (Enterprise) | Scales with organizational complexity. |
| Identity Verification | Email-based JWT + Optional 2FA | Ensures defensible non-repudiation. |
| Routing Depth | Unlimited stages | Supports complex corporate approval chains. |
Efficiency Pro-Tips for Enterprise Scale
- Contact Synchronization: Utilize the Address Book to rapidly select frequent participants and reduce identity entry errors.
- Signing Groups (Enterprise): Define groups (e.g., "Legal Team") where any member of the group can satisfy the signing requirement on behalf of the entity.
- Bulk Recipient Import: For high-volume distribution (e.g., policy updates), utilize the Bulk Send module to import recipients via CSV.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Recipient not receiving email | Syntax error or SMTP block | Verify address and consult the Deliverability Guide. |
| Wrong person signed | Forwarded link | IUSign tokens are identity-bound. Ensure recipients do not manually forward their private signing links. |
| Routing stuck | Previous signer is inactive | Use the Remind or Correct protocol to bypass or nudge the bottleneck. |