License Assignment
Specify SKU, permitted add-ons, billing responsibility, and whether the license is temporary or permanent.
A formal contract clarifies license entitlements, reduces audit and compliance risk, and sets employee responsibilities for data protection and acceptable use. It documents authorization to access corporate resources, supports enforcement of security controls, and creates an auditable record of consent and acknowledgement.
Typical participants include HR, IT, the employee, and sometimes legal or procurement teams.
These stakeholders each retain portions of the record and may trigger provisioning, audit, or termination workflows.
| Field | Configuration |
|---|---|
| License Field Mapping | Map form SKU to provisioning script or identity group. |
| Approval Routing | Route to manager and IT sequentially before provisioning. |
| Authentication Level | Require email + SMS or SSO for employee signer. |
| Provision Trigger | Auto-create account or queue ticket after certificate of completion. |
Successful digital execution often requires integration between the eSignature platform, HR systems, and Microsoft 365.
Confirm API access, SSO, and appropriate role-based permissions before enabling automation to avoid provisioning errors.
Specify SKU, permitted add-ons, billing responsibility, and whether the license is temporary or permanent.
Define permitted activities, prohibited behaviors, and consequences for misuse of corporate Microsoft 365 resources.
Address data classification, storage locations, backup responsibilities, and required data protection measures.
Require multi-factor authentication, device management, and steps for lost or compromised credentials.
Detail license revocation timing, data export, and employee obligations to return or delete files.
Allocate responsibility for misuse, unauthorized disclosures, third-party claims, and licensing audits.
An IT administrator signs or countersigns when the agreement requires technical approval for provisioning, naming conventions, or license allocations; their approval confirms feasibility and compliance with identity controls.
The employee (or authorized representative) signs to accept acceptable-use terms and security obligations; signature documents consent to monitoring, MFA, and return-of-data conditions.
Set a date by which the employee must sign (e.g., prior to account creation)
Provision licenses within 24–72 hours after completed signatures
Revoke access immediately or within employer-defined timeframe (commonly same day)
Allow X days for employee data export before deletion per company policy
Review assignments annually or upon role change to prevent over-licensing
Employee or manager requests license and provides required information.
Manager and cost-center approvals are recorded to authorize the assignment.
Employee and any countersigners complete the contract and certification.
IT provisions account, enforces MFA, and assigns the license.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |