Understanding Your IAM Plan Allowances

^{* 100 / user / year in Enterprise Pro or Financial Services Pro
▵ More information on a specific eSignature plan can be found} here

While a majority of plan allowances are per user, usage of the allowance is not limited to a specific user but is pooled together for all users associated with the Docusign subscription. For subscriptions longer than one year, plan allowances are also pooled across years and the entire allowance will be available for use from the subscription start date. For mid-term addition of users, the plan allowances are prorated for the subscription term.

Using the Automation Sends plan allowance as an example, a one year subscription for 10 full users will confer 500 Automation Sends over the one year subscription term.

A three year subscription for 10 full users will confer 1,500 Automation Sends available for use at any time during the three year subscription.

To purchase additional capacity beyond the allowance in your plan, contact sales

For definitions of our services, please consult the IAM service schedule or relevant product service schedules for more information. The descriptions below are meant to help describe the plan allowances in the table.

Web App 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 website or mobile application

Automation Sends:

• Sending an agreement for signature via an API call from a 3rd party integration or custom-built integration

• Starting a Maestro workflow via an API call from a 3rd party integration or custom-built integration that sends an agreement for signature

• Sending agreements for signature via the Bulk Send capability. Each recipient who needs to sign 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 Workflow Definitions

  • 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 - Agreement Ingestion:

• 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

• Note: Navigator can only support 10,000 or fewer Docusign historical agreements in a subscription

• To upload additional agreements into Navigator, including agreements outside of Docusign, contact sales

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