Docusign Navigator is the former name for Docusign Agreement Manager, the AI-powered agreement repository inside Docusign IAM (Intelligent Agreement Management). Docusign renamed Navigator to Agreement Manager in 2026, but the job stayed the same: centralize signed agreements, extract structured data from them with AI, and expose that data to other systems through an API.
If you searched "docusign navigator" because a client, a vendor, or your own dashboard suddenly shows "Agreement Manager" instead, you're not missing a new product. You're looking at the same tool with a new label. This guide covers what it does today, what its AI actually extracts, and where it fits next to Docusign Workflow Builder (formerly Maestro) - the workflow engine Baton triggers.
What was Docusign Navigator, and why did it get renamed? #
Docusign Navigator launched as a smart, searchable repository for executed agreements, built to end the problem of signed contracts scattered across email, shared drives, and legacy CLM tools. In its 2026 product naming update, Docusign folded Navigator into the Agreement Manager name, alongside the related switch from Docusign Workflow Builder (formerly Maestro) to Workflow Builder. The underlying Agreement Manager API carries an explicit "formerly Navigator API" label in Docusign's own developer documentation, so if you see either name in the wild, both point to the same product.
What does Docusign Agreement Manager actually do? #
Agreement Manager centralizes completed and historical agreements and uses AI to extract structured information such as parties, renewal dates, obligations, and custom fields. In practice, that means three things:
- It pulls agreements in automatically. Agreements signed through Docusign eSignature sync into Agreement Manager automatically, no manual upload required.
- It ingests what you already have. You can bulk upload historical agreements that were signed outside Docusign, so a legal team migrating off a legacy CLM doesn't lose years of contract history.
- It turns documents into queryable data. Instead of opening a PDF to find a termination clause or a renewal date, you search a structured record.
This matters for the Docusign IAM practitioner audience because Agreement Manager answers a different question than Workflow Builder. Workflow Builder asks "what should happen next in this process." Agreement Manager asks "what's actually in the agreements we already have."
How does Agreement Manager's AI extract data from contracts? #
Agreement Manager's extraction is powered by Docusign Iris, the AI engine behind Docusign IAM. Iris is purpose-built for agreements rather than general-purpose text, which is why Docusign positions it against document-specific competitors rather than general chatbots.
When an agreement lands in Agreement Manager, Iris analyzes it and extracts fields like agreement type, effective and expiration dates, named parties, renewal terms, and obligations. You can also define custom extractions for fields specific to your business, like a maximum liability cap or a named approver, without writing a parser yourself.
What can you build with the Agreement Manager API? #
The Agreement Manager API is the part most relevant if you're an engineer rather than a legal ops user. It's a generally available API that ingests large volumes of agreements into IAM, tracks job and document status, and can trigger downstream workflows when Iris extraction completes.
Three concrete use cases engineers build on it:
- Bulk migration. Pull thousands of legacy contracts out of a shared drive or old CLM and push them into Agreement Manager so the AI can extract terms at scale, rather than someone reading each one by hand.
- Status polling. Track whether a batch ingestion job finished and whether extraction succeeded, before your downstream system treats the data as ready.
- Event-driven follow-up. Fire a downstream action once Iris finishes extracting a specific agreement, for example flagging a contract for legal review if the extracted renewal date falls inside 60 days.
That last capability is the one developers most often confuse with what Baton does, so it's worth being precise about the boundary.
Is Docusign Navigator (Agreement Manager) the same as Docusign Workflow Builder? #
No. They solve different problems inside the same Docusign IAM platform, and the distinction matters if you're deciding where to automate.
| Docusign Agreement Manager (formerly Navigator) | Docusign Workflow Builder (formerly Maestro) | |
|---|---|---|
| Core job | Store, search, and extract data from agreements | Orchestrate the steps of an agreement process |
| Primary input | Completed or historical agreement documents | Events and data from CRMs, HRIS, and other source systems |
| What it produces | Structured contract data and insights | Running envelopes and completed signature steps |
| Who triggers it | Agreement Manager API, bulk upload, or auto-sync from eSignature | Workflow parameters matched from an incoming webhook payload |
If your question is "what does our NDA say about termination," that's Agreement Manager. If your question is "when a deal hits Closed Won in Salesforce, send the contract for signature," that's Workflow Builder.
Where does Baton fit next to Docusign Agreement Manager? #
Baton is a webhook relay. It listens for an event from a source platform like HubSpot, Salesforce, or Greenhouse, verifies the signature, matches the payload to a Workflow Builder workflow's parameters, and triggers that workflow. Baton triggers Workflow Builder workflows, which then create and manage envelopes; it does not read from, write to, or trigger Agreement Manager directly.
That separation is useful to keep straight when you're mapping out an agreement automation stack: Agreement Manager is where completed agreements live and get mined for data, and Workflow Builder, fed by Baton, is where the signing process itself gets kicked off. A deal-stage change in your CRM should trigger a Workflow Builder run through something like Baton's HubSpot integration; what happens to that agreement's data after signature, like extraction, renewal alerts, or reporting, is Agreement Manager's job.
If you're building out the triggering side of that stack and want to see how the webhook verification and parameter-matching actually works end to end, Baton's write-up on why Docusign webhooks fail silently is a good next read, since the same reliability concerns apply whether the trigger is feeding Workflow Builder or any other downstream system.
A worked example: tracking NDA renewals across two tools #
Say your legal team has 400 signed NDAs, some from Docusign eSignature and some uploaded from an old CLM, and the goal is "alert us 60 days before any NDA auto-renews." Here's how the two products split the work:
- Agreement Manager handles the data layer. The 400 NDAs sync in automatically (the Docusign-signed ones) or get bulk uploaded (the legacy ones). Iris extracts the renewal date, the auto-renewal clause, and the counterparty name from each one.
- Your own system or a scheduled job checks that extracted data against today's date to find anything inside the 60-day window. This is a query against Agreement Manager's structured data, not a webhook from a source CRM.
- If the renewal review needs a new signature step (for example, routing an amendment for countersignature), that's where a Workflow Builder run gets triggered, and that's the piece a relay like Baton is built to fire reliably from an upstream event, whether that event is a CRM field change, an internal scheduler, or an approval in a ticketing system.
The point of walking through it this way: Agreement Manager and Workflow Builder are not competitors or substitutes for each other, they're adjacent layers. Confusing "where do I store and mine agreement data" with "how do I kick off the next signature step" is the most common mistake teams make when they first hear "Navigator" and assume it's a workflow tool because it lives inside the same Docusign IAM umbrella.
What should you call it going forward? #
Use "Docusign Agreement Manager" in new documentation, support tickets, and internal runbooks. If you're searching for help and only find old material under "Navigator," know that it's current and the product hasn't changed functionally, only the name has. Docusign's own community and developer docs now use "Agreement Manager (formerly Navigator)" consistently, and that's the safest phrasing if you need both terms to show up in search.
FAQ #
Is Docusign Navigator still a product, or was it discontinued? #
It wasn't discontinued, it was renamed. Docusign Navigator became Docusign Agreement Manager in 2026 as part of a broader product naming update that also renamed Docusign Workflow Builder (formerly Maestro) to Workflow Builder. The functionality is unchanged.
What's the difference between Docusign Navigator and Docusign CLM? #
Agreement Manager (formerly Navigator) is an AI-powered repository built into Docusign IAM that extracts data from executed agreements, including ones ingested from outside Docusign. Docusign CLM is a separate, more full-featured contract lifecycle management product with authoring, redlining, and approval routing built in. Agreement Manager focuses on post-signature data and insight, not drafting or negotiation.
Does Docusign Navigator (Agreement Manager) trigger Docusign workflows? #
The Agreement Manager API can trigger downstream workflows once Iris finishes extracting data from an agreement, which is a post-signature, extraction-driven trigger. That's different from triggering a Workflow Builder run from a CRM event before signature, which is what a webhook relay like Baton does.
What AI powers Docusign Agreement Manager's data extraction? #
Docusign Iris, Docusign's agreement-specific AI engine, powers the extraction and insights inside Agreement Manager, pulling fields like parties, dates, and obligations out of unstructured contract text.
Can I bulk upload old contracts into Docusign Agreement Manager? #
Yes. Agreement Manager supports bulk upload of historical agreements completed outside Docusign, in addition to automatically syncing agreements signed through Docusign eSignature.
Next step #
If you already know where Agreement Manager fits and you're ready to automate the triggering side, that is, firing a Workflow Builder run the moment a deal, offer, or purchase order changes state in your source system, see Baton's integration recipes or wire up your first webhook relay with Baton directly.