Can this be signed electronically?

Yes. Electronic signatures meet U.S. legal standards when intent, consent, signer attribution, and durable record retention are present under the ESIGN Act (15 U.S.C. §7001) and UETA.

When is notarization required?

Most license addenda do not require notarization. If a state statute or the master agreement requires notarization, follow that requirement; real property or court filings are common exceptions.

What identity checks are appropriate?

Use email verification for low-risk adds; use SMS OTP, knowledge-based authentication, or SSO for higher assurance or when required by internal controls.

How do I correct a signed addendum?

Do not alter a signed document. Create a corrective amendment or a new addendum that references the original, then obtain fresh signatures from the same authorized parties.

How can an addendum be revoked?

Revocation should follow terms in the master license and the addendum. Document revocation with a signed amendment and update provisioning and billing records accordingly.

How long are signed copies retained?

Retain signed addenda per your retention policy, typically at least three years from the effective date; HIPAA, IRS, or industry rules may require longer periods.

Electronic Signature
Templates
Miscellaneous
User License Add Template

User License Add Template

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

USER LICENSE ADD TEMPLATE

Parties

This User License Addendum (the "Addendum") is made effective as of between Licensor: and Licensee: .

WHEREAS

WHEREAS, the parties entered into a License Agreement identified as dated (the "Agreement");

WHEREAS, the parties desire to add additional user licenses and to set forth the terms and conditions applicable to such additional users.

Scope of License

1. Grant. Subject to the terms and conditions of the Agreement and this Addendum, Licensor hereby grants Licensee a non-exclusive, non-transferable right to permit the designated Additional Users to access and use the Licensed Software solely for Licensee's internal business purposes, limited to the scope described below.

Describe additional user permissions, modules, or limitations Number of additional user licenses being added User type (check all that apply)

Employee Contractor End User

Payment Terms

Licensee shall pay Licensor for the Additional User Licenses as follows.

One-time or recurring fee per user (USD) Payment schedule and invoicing

Late payments shall accrue interest at the rate of on overdue amounts, or the maximum rate permitted by applicable law, whichever is less. Licensee shall also be responsible for reasonable collection costs and any taxes associated with the fees.

Term and Termination

The additional user licenses granted by this Addendum shall commence on and expire on , unless earlier terminated in accordance with this Addendum or the Agreement.

Either party may terminate this Addendum for convenience upon written notice to the other party given not less than days prior to the intended termination date. Termination for cause shall follow the notice and cure provisions set forth in the Agreement.

Confidentiality

Each party acknowledges that, in connection with this Addendum and performance hereunder, it may receive Confidential Information of the other party. "Confidential Information" means any non-public information disclosed in connection with the Agreement or this Addendum. Each party shall protect Confidential Information with the same degree of care it uses to protect its own confidential information, but in no event less than reasonable care, and shall only use Confidential Information to perform its obligations under the Agreement and this Addendum.

Exceptions to confidentiality (if any)

Representations and Warranties

Each party represents and warrants that it has the full right, power and authority to enter into and perform its obligations under this Addendum, and that the execution and performance of this Addendum will not violate any other agreement by which it is bound.

Governing Law

This Addendum shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles.

Entire Agreement

This Addendum, together with the Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof, and supersedes all prior or contemporaneous agreements, understandings and communications, whether written or oral, relating to such subject matter. In the event of any conflict between the terms of this Addendum and the Agreement, the terms of this Addendum shall control solely with respect to the additional user licenses granted herein.

Miscellaneous

No amendment or modification of this Addendum shall be valid unless in writing and signed by authorized representatives of both parties. If any provision of this Addendum is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

LICENSOR

Printed Name:

By:

Date:

LICENSEE

Printed Name:

By:

Date:

What the User License Add Template Is and When It’s Used

A User License Add Template is a standardized amendment used to add one or more named users, seats, or access rights to an existing software or service license. It records the new user's legal name, user identifier, effective date, license tier or seat class, any additional fees or proration, and the signature of an authorized licensor representative. Organizations use this template to create an auditable record of entitlement changes, maintain consistent licensing data, and reduce disputes about who may access licensed systems.

Why a Formal Add Template Matters

A clear add template documents entitlement changes, aligns billing and access, and limits ambiguity about user rights. It provides evidence of consent and scope that helps prevent billing disputes and supports auditability for compliance and internal controls.

Typical Roles That Complete This Template

Teams and individuals across procurement, IT, licensing, and legal commonly prepare and approve User License Add Templates.

IT Administrator — technical owner who verifies user identifiers and access levels, confirming the correct product SKU and provisioning requirements.
Procurement / Licensing Manager — ensures the add aligns with purchase orders, pricing terms, and invoicing; coordinates approvals with finance.
Corporate Counsel — reviews legal terms, signature authority, and whether amendments require board or delegated approvals.

Use the template to centralize approvals and to create a single record that both operations and finance can reference during audits.

Who Signs and Why

IT Administrator

The IT Administrator submits technical user details and confirms that the named user requires access. They ensure the identifier (username or email) matches the account used for provisioning and describe the access tier.

Corporate Counsel

Corporate Counsel or delegated contract approver validates signature authority, confirms amendment scope aligns with the master license, and ensures no conflicting terms before countersigning.

Security, Audit, and Compliance Elements to Include

Encryption in transit: TLS 1.2 / 1.3

Encryption at rest: AES-256

Audit trail: Timestamps, IP, action log

Access controls: Role-based access, SSO

BAA availability: Required for PHI workflows

Export formats: PDF with certificate

Key Risks and Consequences of Errors

Unauthorized access: License breach, termination risk

Incorrect party: Invalidates amendment

Missing authority: Countersignature required legally

Billing mismatch: Overbilling or underbilling exposure

Data privacy gap: Regulatory exposure for PHI

Retention lapse: Audit or discovery risk

Common Preparation Pitfalls to Avoid

Using an informal email or ticket instead of the template, which creates inconsistent records and complicates billing reconciliation.
Entering a nickname or internal alias rather than the full legal name or verified username, causing provisioning and audit mismatches.
Failing to confirm signing authority, which can render the amendment unenforceable and delay access.
Omitting the effective date or proration terms, producing ambiguity about billing start and entitlement period.

Step-by-Step: Completing a User License Add Template

Follow these sequential actions to complete, sign, and archive the addendum correctly.

01

Prepare document: Select the template and reference the master license.
02

Verify requester: Confirm signatory authority and user identifier.
03

Complete fields: Enter full legal name, user ID, seat type, effective date.
04

Sign and archive: Obtain signatures, save PDF, update license registry.

How Digital Completion and Routing Typically Operate

A standard eSubmission flow reduces friction: upload, assign fields, authenticate, complete, and store.

Upload document: Start with the master and addendum.
Place fields: Add name, date, signature, and conditional fields.
Authenticate signer: Email link or stronger auth as required.
Archive copy: Store signed PDF and audit trail.

Recommended Digital Workflow Settings

Configure authentication, signer order, notifications, and storage before sending the add template for signature.

Field	Configuration
Authentication Method	Email link; SMS OTP or KBA where stronger identity needed
Signer Order	Sequential or parallel depending on approval chain
Notifications	Email reminders and completion alerts to finance and IT
Storage Location	Secure cloud repository with versioning and export

Technical and Integration Considerations

Ensure the eSignature platform supports your file formats, integrations, and authentication needs before sending the addendum.

Formats: PDF, DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: Email, SMS OTP, SSO

Confirm audit trail retention, export options, and any required Business Associate Agreement or data residency settings with your platform administrator.

Comparing Typical eSignature Pricing and Capabilities

Basic vendor differences for common criteria; signNow is listed first per comparison convention.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Real-World Examples of Using an Add Template

These short scenarios show common, practical uses of a User License Add Template in organizational workflows.

Optica Ventures

A portfolio manager completed an add to provision a contractor quickly

added one admin seat for three months
the signed add provided audit evidence for billing and access revocation at term end.

Martin Properties

A property manager used a template to add multiple agents at once

bulk add reduced manual entry
the centralized record prevented duplicate invoices and simplified license reconciliation.

Practical Tips for Accurate and Efficient Completion

Small process improvements reduce errors and speed provisioning.

Use a canonical template

Keep a single approved template centrally stored and update via controlled versioning to avoid inconsistent clauses.

Validate identity

Confirm the new user's identifier and authority before provisioning to prevent orphaned accounts.

Automate proration

Calculate prorated fees automatically to avoid manual billing corrections.

Archive with audit trail

Store signed PDF and metadata (timestamps, signer IP) for compliance and troubleshooting.

Time Considerations and Typical Deadlines

Key timing items include effective date, billing cycles, provisioning windows, and audit retention start dates.

Effective Date:

Use MM/DD/YYYY to align with billing and provisioning

Billing Cycle:

Coordinate add with invoice cycles to prevent double billing

Provisioning Window:

Allow 24–72 hours for automated provisioning systems

Audit Availability:

Ensure signed copy is accessible to auditors within two business days

Record Retention Start:

Retention dates typically begin on the effective date

Frequently Asked Questions and Troubleshooting

Answers to common questions about signing, notarization, revocation, and storage for User License Add Templates.

Need help? Contact support

Can this be signed electronically?
Yes. Electronic signatures meet U.S. legal standards when intent, consent, signer attribution, and durable record retention are present under the ESIGN Act (15 U.S.C. §7001) and UETA.
When is notarization required?
Most license addenda do not require notarization. If a state statute or the master agreement requires notarization, follow that requirement; real property or court filings are common exceptions.
What identity checks are appropriate?
Use email verification for low-risk adds; use SMS OTP, knowledge-based authentication, or SSO for higher assurance or when required by internal controls.
How do I correct a signed addendum?
Do not alter a signed document. Create a corrective amendment or a new addendum that references the original, then obtain fresh signatures from the same authorized parties.
How can an addendum be revoked?
Revocation should follow terms in the master license and the addendum. Document revocation with a signed amendment and update provisioning and billing records accordingly.
How long are signed copies retained?
Retain signed addenda per your retention policy, typically at least three years from the effective date; HIPAA, IRS, or industry rules may require longer periods.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now