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, please note that the following changes have been made:

• Customers with an Order Start Date on or after 28 August 2024, 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. Those same Customers with IAM Enterprise, IAM for Sales or IAM for CX on their subscription also have Automation Sends from a third-party integration excluded from the allowance. 

• Customers with an Order Start Date on or after 4 December 2024, with an IAM Standard, IAM Professional, IAM Enterprise or IAM for Sales plan on their subscription, have the new Agreement Manager document allowance of 500 documents per user per year.

• Customers with an Order Start Date on or after 9 April 2025, with an IAM Standard, IAM Professional, IAM Enterprise or IAM for Sales plan on their subscription, will receive an increase in the Agreement Manager document allowance to 1,000 per user per year. 

• Customers with an Order Start Date on or after 9 April 2025, with an IAM Starter, IAM Standard, IAM Professional, IAM Enterprise or IAM for Sales plan on their subscription, will receive a one-time, non-renewable increase in the Agreement Manager document allowance to 5,000 agreements per user.

• Customers with an Order Start Date on or after 21 November 2025, with an IAM Starter, IAM Standard, IAM Professional, IAM Enterprise or IAM for Sales plan on their subscription, will no longer have a limit on Agreement Manager Ongoing Agreements. Customers will continue to be bound by the Automation Sends allowance of 100 per user per year, pooled at the account level. Those same Customers will also receive a new allowance for usage of the Custom Extractions feature in Agreement Manager, and an updated allowance for usage of workflows in Workflow Builder.

• Customers with an Order Start Date on or after 20 February 2026, with an IAM Enterprise, IAM for Sales or IAM for CX plan on their subscription will have a new allowance of sends from a third-party integration of 200 sends per user per year, pooled at the account level.

¹ _{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 third-party integration do not count towards the plan allowance. Customers do not have access to other IAM capabilities listed.}

³_{Subject to an allowance of 200 sends per user per year, pooled at the account level.}

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, to add additional users or for further help understanding the usage allowances, please contact sales.

The information below is provided for illustrative purposes only and to further help describe the plan allowances shown 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 Workflow Builder workflow that sends an agreement for signature using the Docusign web application or mobile application

• Note: Bulk Send is counted as 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 Workflow Builder 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 third-party service is counted as an Automation Send in IAM Standard and IAM Professional

• Starting a Workflow Builder 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 is counted as one Automation Send. As an approximation, each row with data (excluding the header) in the Bulk Send template is counted as one Automation Send.

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

Workflow Builder Workflows:

• Workflow Builder Workflows

  • Only published workflows will count towards your plan allowance.Note: Workflow Builder workflows are flexible with conditional content, so as an example, you can use the same HR onboarding workflow across multiple different onboarding scenarios.

• Workflow Builder Workflow Runs

  • A Workflow Builder 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 Workflow Builder workflow is counted as one Workflow Builder run. For example, if an HR admin kicks off onboarding an employee, each triggered Workflow Builder workflow counts as one run.

Agreement Manager Documents:

• An Agreement Manager Document is an IAM Agreement that has been ingested into Docusign Agreement Manager.

• When an IAM agreement is made available in Docusign Agreement Manager, that document counts towards the plan allowance.

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

• When upgrading from an eSign plan to an IAM plan, any existing IAM Agreements from completed envelopes ingested into Docusign Agreement Manager will count towards the plan allowance.

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

• Your Agreement Manager Documents can be found in the Agreement Manager section under the documents tab.

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

Agreement Manager - Documents Processed:

• In Agreement Manager, customers can use the Custom Extractions feature to instruct Docusign’s AI engine to identify custom agreement types and detect custom field data within their signed eDocuments. Unlike the standard, out-of-the-box AI-assisted data extractions, custom extractions are created and configured by the Authorised User.

• Document Processed refers to an Agreement Manager document that has been fully analysed by Docusign's AI engine to identify custom extractions created and configured by the Authorised User. Agreement processing can be triggered in two distinct ways:

  • Historical Reprocessing refers to when an Authorised User creates and activates AI detection for a new custom extraction and initiates processing across their entire portfolio of agreements already stored in Agreement Manager to ensure the new custom extraction is applied historically.

  • New Ingestion Processing refers to when a user creates and activates AI detection for a new custom extraction that enables AI to automatically identify and detect the new custom extraction on any newly signed agreements stored in Agreement Manager going forward.

Document Generation for eSignature:

• Generation of an agreement from a template marked with the Document Generation badge and sent for signature will be counted from the plan allowance

• Creating or building a template will not be counted from the plan allowance for Document Generation

• Creating an agreement from a template without the Document Generation badge will not be counted from 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 the bank account, bank account holder, business entity or SSN, verified in field groups or a form will be counted from the plan allowance (US availability only)

• Basic Data Verification like phone number, email or address will not be counted from the plan allowance

• Note: Premium Data Verification will only be counted from the plan allowance once the recipient's entered data has been verified or the recipient has exceeded the allowed number of attempts

ID Verification and Knowledge-Based Authentication (KBA):

• Each time a recipient starts the ID Verification or KBA process by selecting an ID method it will be counted from the plan allowance

• Each time a participant in a Workflow Builder workflow starts the ID Verification or KBA process by selecting an ID method, it will count towards 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 it will be counted from the plan allowance

• Each time a participant in a Workflow Builder workflow starts the SMS or Phone Authentication process by electing to receive a text message or automated phone call