This guide provides technical instructions for the formal invitation and onboarding of new team members into an IUSign Enterprise environment.
Prerequisites
- Assigned Admin or Owner role within the tenant.
- Available "seats" within the active subscription tier.
- Valid corporate email addresses for the target invitees.
Strategic Overview
Scaling an organization's digital signature capability requires a structured approach to identity provisioning. IUSign allows administrators to invite users into a centralized organizational tenant, ensuring that all document activity is governed by a unified security policy and branding profile. By onboarding team members into a shared environment, organizations can leverage collaborative features such as shared templates, centralized repository access, and consolidated billing.
Implementation Sequence
1. Initialization of the Invitation Protocol
Navigate to the Admin Dashboard and select the Users module. Click on Invite Team Member to initialize the provisioning wizard.
2. Specification of Identity Parameters
Specify the primary identity parameters for the new team members:
- Email Identities: You can input multiple email addresses separated by commas to perform a Batch Invitation.
- Role Designation: Assign a baseline role (e.g., User, Admin, or Viewer) that will apply to this batch of invitees.
- Custom Message: Optionally append a personal note to the invitation email to provide context regarding the onboarding process.
3. Dispatch and Cryptographic Handshake
Upon selecting Send Invitations, the IUSign engine executes the following:
- Token Synthesis: A unique, high-entropy onboarding token is generated for each email identity.
- SMTP Dispatch: Invitations are sent via secure SMTP channels.
- Pending State: The new identities appear in the user list with a Pending status until the recipient accepts the invitation.
4. Recipient Acceptance and Onboarding
The invitee receives an email with a secure link. Upon selection:
- Identity Alignment: The recipient is guided through the Account Creation or login process.
- Tenant Binding: Their identity is cryptographically bound to your organizational tenant.
- Role Activation: Their assigned permissions are immediately activated.
Technical Specifications: Invitation Lifecycle
| Feature | Technical Detail |
|---|---|
| Token Validity | 7 Days (168 hours) from issuance. |
| Batch Capacity | Up to 50 invitations per individual batch. |
| Security Link | One-time use; invalidated upon successful onboarding. |
| Audit Trace | The TEAM_INVITATION_SENT event is recorded in the global audit log. |
Strategic Considerations for Administrators
- Domain Auto-Join: For Enterprise tenants, consider enabling Domain Auto-Join. This allows users with a specific corporate domain (e.g.,
@yourcompany.com) to join the organization automatically without a manual invitation. - Role Re-Evaluation: After onboarding, review the user's activity to ensure their assigned role aligns with their actual operational requirements.
- Invitation Maintenance: Monitor the Pending list. If an invitation remains unaccepted after 3 days, utilize the Resend Invitation action to nudge the recipient.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Invitation expired | Temporal decay | Locate the user in the "Pending" list and select Resend Invitation to generate a new token. |
| Email already registered | User is in another tenant | The user can still join your organization; IUSign supports multi-tenant identity association. |
| Seat limit reached | Tier capacity violation | Upgrade your plan or deactivate inactive users before sending new invitations. |