
Docusign is retiring the Connect Publish page on November 18, 2026, moving all manual republish functionality into the Connect Dashboard, and the Connect Logs page is scheduled to follow it into retirement sometime in 2027, according to Docusign's eSignature 26.3.02.00 release notes for November 2026. If your team scripts against those legacy pages, or trains support staff to debug failed webhooks there, that workflow needs to move to the Connect Dashboard and the Connect REST API before the cutover.
This is a small UI change on paper. In practice, it is the kind of change that quietly breaks a runbook six months after everyone has forgotten it exists, usually when a webhook starts failing at 2am and the on-call engineer opens a bookmark that now 404s.
Docusign Connect is the webhook service that notifies your application when envelope events happen, such as a recipient signing or a document completing, instead of forcing you to poll the Docusign API on a schedule. Two legacy admin pages inside Connect are being retired:
Both are being folded into the modern Connect Dashboard, which Docusign has been building out since early 2026. This is not the first legacy Connect page to go: the old Failures page was already deprecated in the March 2026 (26.1.00.00) release and replaced entirely by the dashboard.
Docusign has spent most of 2026 consolidating Connect administration into one dashboard instead of three or four separate screens. The pattern is consistent across the year's release notes:
Read together, this is Docusign closing the gap between "things the old pages could do" and "things the dashboard can do," then removing the old pages once the gap is closed. The Logs page is next because its one remaining job, letting you drill into a specific delivery failure, is now covered by the dashboard's expanded log detail.
Three things break in practice, and none of them are obvious until the deadline passes:
1. Bookmarked admin URLs stop resolving. Any support runbook, onboarding doc, or internal wiki page that links directly to Admin > Connect > Publish will point at a page that no longer exists. If your support team's "how to manually republish a stuck envelope" doc has a screenshot of that page, it is wrong on November 19.
2. Browser automation and screen-scraping scripts fail outright. Some teams, especially ones that inherited a Connect integration rather than building it, automated the Publish page itself with a headless browser script to bulk-republish envelopes on a schedule. That script has no fallback once the page is gone; it will throw a 404 or a selector-not-found error with no warning beyond the release notes.
3. Training materials and SOPs reference a workflow that moved. The capability to republish envelopes is not going away, only the page. Anyone who was taught "go to the Publish tab, check the boxes, click Publish" now needs to be taught the dashboard's republish flow instead, which supports the same per-envelope and CSV-based bulk republish Docusign describes in the November 2026 notes.
None of this breaks your actual webhook delivery. Docusign is not changing how Connect sends events, verifies payloads, or retries failures: it's changing where you go to manage and inspect that activity.
If your team automated the Publish page with browser scripting, the fix is to stop scripting a UI and start calling the actual API endpoint behind it. Docusign's Connect REST API includes a historical publish resource for exactly this purpose: resubmitting existing envelope data to a Connect configuration without re-triggering the original envelope workflow, documented in the Connect category reference.
A minimal republish call looks like this:
curl -X PUT \
"https://{BASE_URI}/restapi/v2.1/accounts/{ACCOUNT_ID}/connect/envelopes/publish/historical" \
-H "Authorization: Bearer {ACCESS_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"fromDate": "2026-11-01T00:00:00Z",
"toDate": "2026-11-17T23:59:59Z",
"connectId": "{YOUR_CONNECT_CONFIG_ID}"
}'This is the same operation the Publish page's "select by date range" option performed, just callable from a script, a scheduled job, or a CI pipeline instead of a browser. It is also more auditable: the call lives in your deployment logs instead of in a person's browser history.
If your use case is per-envelope rather than per-date-range, the same resource family accepts a list of specific envelope IDs, which maps to the Publish page's checkbox selection flow.
Docusign has not published an exact 2027 date yet, only that the Logs page will be deprecated later in 2027. Treat that as a planning signal, not an emergency: you have more runway than you do for the Publish page, but the underlying advice is the same. Stop pointing anyone, human or script, at the standalone Logs page and start using the Connect Dashboard's log detail view, which already carries more data per event than the legacy page did after the March 2026 upgrade.
If your team has a support macro, a canned response, or a debugging checklist that says "check the Connect Logs page," update it now while the old page is still live and you can screenshot the new one side by side. Waiting until the actual 2027 deprecation date means doing this update under pressure instead of on your own schedule.
Treat this like any dependency on a UI you don't control:
Connect > Publish or Connect > Logs.This is also a reasonable moment to ask a broader question: if the only reliability layer between your source systems and Docusign Connect is "someone notices a failure in the dashboard and manually republishes," you're relying on a human catching something that automation should be catching. Docusign's own auto-retry enforcement from April 2026 covers transient network failures, but it doesn't cover logic errors in your receiving endpoint, downstream outages, or the need for centralized logging across every workflow that triggers a Docusign envelope in the first place.
Teams that trigger Docusign Workflow Builder (formerly Maestro) runs or Connect webhooks from source platforms like HubSpot, Salesforce, or an internal system often end up owning two separate reliability problems: making sure Docusign's webhook reaches them, and making sure their own system's outbound call to trigger a workflow succeeds in the first place. Docusign's Connect Dashboard solves the first half, inbound delivery and republish, for Docusign events specifically.
For the other half, relaying webhooks reliably between a source platform and Docusign with HMAC verification, retries, and centralized logging, that's the problem Baton is built to solve as a dedicated webhook relay layer, so you're not rebuilding that infrastructure inside every integration. If your team is debugging Connect failures today because a workflow trigger silently dropped upstream of Docusign entirely, that's usually a Baton-shaped gap, not a Connect-shaped one.
For the Docusign side specifically, fluidlabs has a deeper walkthrough of the Connect Dashboard and webhook management patterns worth reading alongside this one, and our resources index tracks every Docusign Connect and Workflow Builder change as it ships.
When exactly is the Connect Publish page being deprecated? November 18, 2026, per Docusign's eSignature 26.3.02.00 release notes for November 2026.
Is the Connect Logs page being removed at the same time? No. The Logs page is scheduled for deprecation later in 2027, on a separate and later timeline than the Publish page.
Will my Connect webhooks stop working when the Publish page is removed? No. This change only affects the manual republish and log-viewing UI. Docusign is not changing how Connect delivers, retries, or signs webhook events as part of this deprecation.
What replaces the Publish page's functionality? The Connect Dashboard now supports direct republish, including CSV-based bulk republish, and the Connect REST API's historical publish resource supports the same operation programmatically.
Did Docusign deprecate any other Connect pages recently? Yes. The legacy Connect Failures page was deprecated in March 2026 and replaced by the dashboard, the same pattern now being applied to Publish and Logs.
If your team is still auditing which Docusign Connect workflows touch the Publish or Logs pages, or you want a second set of eyes on your webhook architecture before the cutover, book a working session with the fluidlabs team to walk through your Connect configuration and migration plan.
Thirty minutes with an engineer. Within 48 hours you get a scoped plan and a fixed price in writing, or a straight “you don't need us.” No charge, nothing to sign.
Talk to an engineer →or email us at hello@fluidlabs.com