This guide provides technical instructions for recipients assigned as "Receives a Copy" (CC) within an IUSign document workflow.
Prerequisites
- A valid IUSign CC notification received via a cryptographically signed SMTP channel.
- Note: CC recipients are typically notified only after the document has been fully executed by all signatories.
Strategic Overview
The Carbon Copy (CC) role is designed for stakeholders who require visibility into a transaction without the authority or obligation to execute signatures or input data. In the IUSign ecosystem, CC recipients serve as observers who maintain a forensic copy of the finalized agreement. This role is essential for legal departments, departmental managers, and administrative stakeholders who need to archive completed documents within their own localized repositories or record-keeping systems.
Functional Workflow for CC Recipients
1. Notification and Ingress
Once the document reaches its final stage (either immediately upon dispatch or after all signatures are collected, depending on the Routing Order), the CC recipient receives an automated notification. This email contains a secure link to view the finalized assets.
2. High-Fidelity Visualization
Selecting the link initializes the Secure Review Portal. This interface provides a full-fidelity, read-only view of the document.
- Signature Review: Observe all executed signatures, initials, and date fields.
- Data Audit: Review all information input by signatories during the execution phase.
- Packet Context: If the envelope contains multiple documents, the CC recipient can navigate through the entire packet in its finalized state.
3. Asset Retrieval and Export
The primary function of the CC role is archival. Within the Review Portal, select Download to retrieve the finalized assets:
- Signed PDF: The document with all signatures and the IUSign security seal embedded.
- Certificate of Completion: The forensic audit record detailing the entire transaction lifecycle.
Data Visibility and Forensic Impact
| Component | CC Recipient Access | Rationale |
|---|---|---|
| Document Content | Full Read Access | Required for auditing and archival. |
| Signer Inputs | Full Read Access | Verification of terms and data. |
| Audit Trail | Full Read Access | Transparency into the chain of custody. |
| Signing Fields | Zero Write Access | CC role is non-participatory by design. |
Strategic Considerations for CC Recipients
- Audit Integration: CC recipients should verify the digital seal of the downloaded document using a standard PDF validator to ensure the record is authentic before archiving.
- Notification Timing: If you are a CC recipient in a Sequential Workflow, you may not receive your copy until all previous signatories have completed their requirements.
- Permanent Access: It is recommended to download the assets immediately upon receipt, as the secure link may expire after the organizational Retention Window.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Document not yet received | Workflow pending | The document may still be awaiting signatures from other parties in the routing order. |
| Access denied | Security timeout | The secure link may have expired or the envelope was Voided. Contact the sender. |
| Cannot find download | Portal interface | Ensure you are viewing the document in a supported browser; the download action is typically located in the header. |