Understanding Your IAM and eSignature Plan Allowances

For customers who purchased a Docusign service subscription from a Docusign sales representative or Docusign Partner, Docusign’s IAM and eSignature plans and applications include various features with applicable usage allowances as shown below.  For customers purchasing a Docusign service subscription plan from our website, please refer to the Docusign Plans and Pricing page for the applicable information regarding web-based plan allowances.

To keep you informed about your plans and allowances, the following changes have been made:

• On August 28, 2024 all customers with an IAM Standard, IAM Professional, IAM Enterprise, IAM for Sales, or IAM for CX plan on their subscription received an increase to the Automation Sends allowance from 50 / user / year to the current amount of 100 / user / year. Customers with IAM Enterprise, IAM for Sales, or IAM for CX on their subscription also have Automation Sends from a 3rd party integration excluded from the allowance. 

• On December 4, 2024 all customers with an IAM Standard, IAM Professional, IAM Enterprise, or IAM for Sales plan on their subscription will have the new Navigator Agreements plan allowance.
  
  

^{* 100 / user / year in Enterprise Pro or Financial Services Pro
▵ More information on a specific eSignature plan can be found} here
^{⧫ Customers with eSignature Unlimited Web-app sends subscriptions have unlimited web-app sends and 100 Automation Sends per user per year pooled at the account level (as detailed below). For customers with eSignature Enterprise Pro Edition - Unlimited Web-app Sends plans, sends from a 3rd party integration do not count against the plan allowance‡. Customers do not have access to other IAM capabilities listed.
‡ Subject to a rate limit of 50 / user / day}

Additional Allowance Details:

Usage of the allowance is pooled together for all user seats purchased with the Docusign subscription. For subscriptions longer than one year, the entire plan allowance is available for use during the entire subscription term (e.g., from the Order Start Date listed on the Order Form).

Using the Automation Sends plan allowance as an example:

• A one year subscription term for 10 full users will confer an entitlement of 1,000 Automation Sends over the one year subscription term.

• A three year subscription term for 10 full users will confer an entitlement of 3,000 Automation Sends available for use at any time during the three year subscription.

To purchase additional entitlements beyond the allowance in your plan, add additional users, or for further help understanding the usage allowances please contact sales.

The information below is provided for illustrative purposes only and meant to further help describe the plan allowances in the table.  Refer to the IAM service schedule and other relevant product service schedules for applicable service terms.

Web Application Envelopes

• Sending an agreement for signature using the Docusign web application or mobile application

• Starting a Maestro workflow that sends an agreement for signature using the Docusign web application or mobile application

• Note: Bulk Send is counted towards Automation sends, not Web application envelopes

Automation Sends:

• Sending an agreement for signature via an API call or integration from a customer built integration

• Starting a Maestro workflow via an API call or integration from a customer built integration that sends an agreement for signature

• Sending an agreement for signature via an API call or integration from a 3rd party service counts as an automation sends in IAM Standard and IAM Professional

• Starting a Maestro workflow via an API call or an integration from a 3rd party service that sends an agreement for signature counts as an automation send in IAM Standard and IAM Professional

• Sending agreements for signature via the Bulk Send capability. Each envelope requiring signature counts as one Automation Send. As an approximation, each row with data (excluding the header) in the Bulk Send template counts as an Automation Send

• A Web Form or PowerForm resulting in a send for signature

Maestro Workflows:

• Maestro Workflows

  • Only published workflows count towards your allotted capacity within your plan.
    Note: Maestro Workflows are flexible with conditional content, so as an example, you can use the same HR onboarding workflow across multiple and different onboarding scenarios.

• Maestro Workflow Runs

  • A Maestro Workflow once published can be initiated by any user with the right access, e.g. sender, end-user, or via an API call. Each such trigger of a published Maestro Workflow is counted as one Maestro Run. For example, if an HR admin kicks off onboarding an employee, each triggered Maestro Workflow counts as one run.

Navigator Agreements:

• A Navigator Agreement is an IAM Agreement that has been ingested into Docusign Navigator.

• When an IAM agreement is made available in Docusign Navigator, that agreement counts against the plan allowance.

• IAM Agreements are ingested into Docusign Navigator primarily, but not exclusively, through completed envelopes, bulk upload, or individual upload.

• Upon upgrading from an eSign plan to an IAM plan, any existing IAM Agreements from completed envelopes ingested into Docusign Navigator will count against the plan allowance.

• As a reminder, Docusign Navigator uses AI Services to extract insights from the contents of agreements.

• Your Navigator Agreements can be found in the Navigator section under the agreements tab.

• Upon upgrading to an IAM plan, agreements from completed envelopes currently in an existing Docusign customer’s eSignature account will be ingested automatically into Navigator. Each ingested agreement counts against the plan allowance.

Document Generation for eSignature:

• Generation of an agreement from a template marked with the Document Generation badge and sent for signature counts against the plan allowance

• Creating or building a template does not count against the plan allowance for Document Generation

• Creating an agreement from a template without the Document Generation badge does not count against the plan allowance for Document Generation

Premium Data Verification:

• A recipient of an agreement enters data into a field or form which is verified in real-time.
  Recipient data such as Bank Account, Bank Account Owner, Business Entity, or SSN, verified in field groups or a form count against the plan allowance (US availability only)

• Basic Data Verification like Phone number, email, or address do not count against the plan allowance

• Note: a premium data verification counts against the plan allowance only when the recipient entered data is verified or the recipient exhausts the allowed attempts

ID Verification and Knowledge-Based Authentication (KBA):

• Each time a recipient starts the ID Verification or KBA process by selecting an ID method, counts against the plan allowance

• Each time a participant in a Maestro workflow starts the ID Verification or KBA process by selecting an ID method, counts against the plan allowance

• Note: For availability of certain ID verification methods, please refer to our support article

SMS or Phone Authentication:

• Each time a recipient starts the SMS or Phone Authentication process by electing to receive a Text Message or Automated Phone Call, counts against the plan allowance

• Each time a participant in a Maestro workflow starts the SMS or Phone Authentication process by electing to receive a Text Message or Automated Phone Call