This guide provides technical instructions for the granular configuration and security management of Public Signing Links within the IUSign Enterprise platform.
Prerequisites
- Active Solo, Growth, or Enterprise subscription tier.
- Assigned Admin or Owner role.
- An existing Public Signing Link.
Strategic Overview
Public Links are high-exposure entry points into your organizational document repository. Proper configuration of Link Settings is essential for ensuring that mass-distributed documents remain secure, compliant, and integrated with your internal business logic. From these settings, administrators can control the lifecycle of the link, enforce specific identity verification protocols, and define post-completion behavior (such as custom redirections). These controls provide the necessary governance for high-volume, automated signature workflows.
Core Configuration Modules
1. Security and Identity Verification
Define the friction level and identity rigor for the public entry point:
- Email Verification (OTP): Mandatory for all Public Links. Ensures the recipient has access to the email address they provide, binding the signature to a verified identity.
- Access Code (Optional): Require users to input a pre-defined password before entering the signing portal. This is ideal for distributing links to a specific semi-public group (e.g., attendees of a private event).
2. Lifecycle and Interaction Limits
Manage the availability of the link to prevent unauthorized volume or temporal decay:
- Expiration Date: Set a specific date and time after which the link will automatically deactivate.
- Signature Quota: Define a maximum number of completed documents (e.g., "Stop after 500 signatures"). This is critical for managing promotional offers or fixed-capacity events.
- Active Toggle: Manually activate or deactivate the link at any time without deleting the historical data.
3. Post-Completion Orchestration
Control the user's experience after they successfully execute the document:
- Post-Sign Redirect URL: Automatically redirect the user to a specific webpage (e.g., a "Thank You" page on your website or a secondary registration form) after they select "Finish."
- Automatic Archival: Define which Document Folder completions should be routed to for simplified reporting.
Technical Specifications: Link Metadata
| Parameter | Functional Impact | Rationale |
|---|---|---|
| Link Slug | Customizes the URL (e.g., /sign/waiver-2026). | Enhances brand trust and legibility. |
| Source Template | Immutable anchor for the link assets. | Ensures all signers receive the same version. |
| CC Recipients | Automated copy distribution. | Notifies internal teams of each completion. |
| White-Labeling | Applies organizational theme. | Provides a unified corporate experience. |
Strategic Considerations for Administrators
- Version Control: If you update your Document Template, remember to verify if your Public Link settings need adjustment to reflect changes in recipient roles or field requirements.
- Data Isolation: Utilize different Public Links for different marketing channels or physical locations (via unique QR codes) to enable granular Performance Analytics.
- Resource Management: Monitor your signature quota settings to ensure you do not exceed your organizational Tier Limits during high-volume periods.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Link shows "Quota Reached" | Signature limit reached | Increase the "Signature Quota" in the link settings or upgrade your plan if you have reached the tier maximum. |
| Redirect not working | Invalid URL syntax | Ensure the Redirect URL is a full absolute path beginning with https://. |
| CC recipients not notified | SMTP/Permission error | Verify the email addresses in the CC list and ensure they have Viewer or Admin roles. |