The Docusign IAM platform, short for Intelligent Agreement Management, is Docusign's unified agreement system that bundles eSignature, workflow automation, an AI-powered agreement repository, and a connector marketplace into one product line. Docusign launched IAM on April 11, 2024, positioning it as a new software category rather than an upgrade to eSignature alone. If you came here trying to figure out what you actually get when someone says "we're on Docusign IAM," this is the map.
What does "IAM" stand for in Docusign? #
IAM stands for Intelligent Agreement Management. Docusign coined the term to describe a platform that handles the entire agreement lifecycle, not just the signature moment: preparing a document, routing it for approval, collecting signatures, storing the executed copy, and acting on the data inside it. Docusign's own framing is that most businesses lose value to what it calls the "agreement trap," which it estimates costs organizations roughly $2 trillion in lost global economic value each year. That number comes from Docusign, not an independent audit, so treat it as a vendor framing claim rather than a verified industry statistic.
What's actually inside the Docusign IAM platform? #
IAM is not one app. It is a set of products that share the same account, data layer, and security model. The core pieces are:
- Docusign eSignature. The signature and sending product most teams already know. eSignature is included in every IAM plan, so moving to IAM never means losing eSignature functionality.
- Docusign Workflow Builder (formerly Maestro). A no-code workflow engine that chains steps before and after signature together: pulling data from a CRM, routing for internal approval, generating a document, sending for signature, then pushing the result somewhere else. Docusign's own community material now refers to the product as "Workflow Builder (formerly Maestro)" after the rename.
- Docusign Agreement Manager (formerly Navigator). An AI-powered repository that ingests signed agreements and extracts structured data, parties, dates, renewal terms, obligations, so legal and ops teams can search and report on agreements instead of hunting through PDFs. The rename from Navigator to Agreement Manager is documented in Docusign's own community posts; we covered the full rename in our breakdown of what changed.
- Docusign Iris. The AI engine that powers extraction in Agreement Manager and other AI features across the platform. Docusign describes Iris as the AI engine behind IAM, not a separate purchasable product.
- App Center. Docusign's marketplace for connecting third-party systems into IAM workflows. Docusign advertises more than 1,000 partner integrations available through App Center and its APIs.
- Docusign CLM. The contract lifecycle management product for teams that need deeper clause libraries, redlining, and obligation tracking than Agreement Manager provides on its own. CLM is sold as an add-on inside the IAM portfolio rather than a default component.
How is Docusign IAM different from Docusign eSignature alone? #
eSignature answers one question: how does this document get signed? IAM answers a bigger one: what happens to this agreement before and after the signature. If your process stops at "send, sign, done," plain eSignature is enough. If you need the agreement to trigger a provisioning step, update a CRM field, kick off an approval chain, or get mined for renewal dates six months later, that is IAM territory, specifically Workflow Builder and Agreement Manager working on top of eSignature's signing engine.
How do you trigger Docusign IAM workflows from your other systems? #
This is where most IAM rollouts get stuck. Workflow Builder can start a workflow a few ways: manually, on a schedule, or from an event in another system. For that last option, Docusign expects you to either build against its webhook and Connect infrastructure or wire up a relay that listens for events in your CRM, HR system, or procurement tool and calls the right Workflow Builder workflow with the right parameters.
That relay step is exactly what Baton does: it sits between a source platform like HubSpot or Salesforce and Docusign Workflow Builder, verifies the incoming webhook's HMAC signature the same way Docusign's own Connect docs specify, matches the payload fields to a workflow's parameters automatically, and triggers the workflow. Baton does not store credentials for the source platform and does not push data back into it; it only handles the one-directional trigger path into Workflow Builder. If you are evaluating how to connect a specific CRM, see our recipe for triggering Docusign workflows from HubSpot for a worked example.
Does Docusign IAM replace Docusign Connect? #
No. Docusign Connect is Docusign's event-delivery system for envelope and document events (an envelope was sent, viewed, signed, declined). IAM's Workflow Builder is a separate execution layer that runs multi-step automations. They can work together, but a Workflow Builder trigger failing silently is a different failure domain than a missed Connect event, and troubleshooting each requires looking at different logs. We go deeper on the trigger-reliability side in why Docusign webhooks fail silently.
Is Docusign IAM worth adopting if you already use eSignature? #
That depends on how much manual work happens around your signatures today. Docusign has said IAM became its fastest-growing product line, powering over 20% of new direct-customer deals by the fourth quarter of its fiscal 2025, which suggests a real pull toward the bundled model among new buyers, though that figure describes new-deal mix, not a guarantee of value for every existing eSignature customer. If your team is manually copying signed-agreement data into a CRM or spreadsheet after every signature, or manually kicking off approval chains before a document goes out, that manual work is the signal that Workflow Builder and Agreement Manager will pay for themselves. If your process genuinely begins and ends at the signature, eSignature alone may still be the right scope.
How is Docusign IAM packaged and priced? #
Docusign does not sell IAM as a single SKU. It sells tiered plans, Docusign's own product pages reference an IAM Starter tier as the entry point, with higher tiers unlocking more of Workflow Builder, Agreement Manager, and CLM. Because Docusign changes plan names and inclusions more often than most vendors, treat any specific tier name or price you read (including here) as a snapshot, and confirm current packaging on Docusign's own pricing page before you budget a rollout. The one stable fact across every tier: eSignature ships in all of them, so IAM is additive on top of what you already pay for, not a separate product you adopt in place of eSignature.
eSignature alone vs. Docusign IAM: what actually changes #
| Capability | eSignature only | Docusign IAM |
|---|---|---|
| Send a document for signature | Yes | Yes |
| Track signer status and reminders | Yes | Yes |
| Trigger multi-step automation before/after signing | No | Yes, via Workflow Builder |
| AI extraction of terms from signed agreements | No | Yes, via Agreement Manager and Iris |
| Pre-built connectors to CRMs, HRIS, and procurement tools | Limited | Yes, via App Center |
| Centralized, searchable agreement repository | No | Yes, via Agreement Manager |
The practical read: if every row on the right already matches what you do manually in a spreadsheet or inbox, IAM is replacing that manual layer with a system of record. If you only ever needed signatures, the extra rows are capability you are not using yet.
What does a Docusign IAM trigger path look like end to end? #
A typical IAM automation has three stages, and knowing which stage you are debugging saves hours:
- Event stage. Something happens in a source system, a deal closes in a CRM, a candidate accepts an offer in an ATS, a PO gets approved in a procurement tool. That system fires a webhook.
- Trigger stage. Something receives the webhook, checks it is genuine, and calls the matching Workflow Builder workflow with the right parameters. This is the stage Baton occupies: HMAC verification, payload-to-parameter matching, and the actual workflow trigger call.
- Workflow stage. Workflow Builder runs its configured steps: generate a document, route for approval, send for signature, write results out. This is entirely inside Docusign, governed by the Workflow Builder developer docs.
When something goes wrong, the fix depends on which stage failed. A silent failure at the event or trigger stage looks identical to the business user as a workflow that "just didn't start," but the root cause and the fix are completely different from a workflow that started and then stalled on an approval step. Treating all three stages as one black box is the single biggest reason IAM rollouts stay hard to support.
What should you do next? #
If you are past the "what is IAM" question and into "how do I connect it to the system my team already lives in," the practical next step is deciding how events reach Workflow Builder reliably. Browse the Baton resources library for integration-specific guides, or wire up your first trigger with Baton if you already know which source platform needs to talk to Docusign IAM.
FAQ #
What does IAM stand for in Docusign? #
IAM stands for Intelligent Agreement Management. Docusign introduced it as a new product category in April 2024, covering the full agreement lifecycle rather than just signing.
Is eSignature included in Docusign IAM? #
Yes. eSignature is part of every IAM plan; you are not asked to give it up or buy it separately when you move to IAM.
What happened to Docusign Docusign Workflow Builder (formerly Maestro)? #
Docusign renamed Docusign Workflow Builder (formerly Maestro) to Workflow Builder. Docusign's own support and community content now uses the bridging form "Workflow Builder (formerly Maestro)" so search traffic for the old name still finds the product.
What happened to Docusign Navigator? #
Navigator was renamed Agreement Manager. The product still does the same job, an AI-powered repository for executed agreements, under the new name. We cover the full rename, including what stayed the same, in a dedicated breakdown.
How do I trigger a Docusign IAM workflow from my CRM? #
You need an event source, typically a webhook from your CRM, and something that verifies the webhook and calls the right Workflow Builder workflow with the matching parameters. Baton is built specifically for that trigger step between source platforms and Docusign Workflow Builder.
Does Docusign IAM replace Docusign Connect? #
No. Connect delivers envelope and document events; Workflow Builder executes multi-step automations. They solve different problems and fail in different ways, so monitor them separately. See Docusign's Connect webhook docs for the event-delivery side.