Oct 2, 2026 - eSign on Forge release (v3) is now GA (General Availability) following a successful 90 day Early Access period. It is a recommended upgrade for all customers from your Atlassian App Management console.
The Atlassian Marketplace and Developer ecosystem is evolving from Connect Apps to Forge Apps. To align with Atlassian guidance and receive the benefits of improved support, reliability and security, eSign for Confluence is migrating to the Forge platform in 2026.
What this means to existing eSign Customers and Users:
-
The overall signature experience and data are unchanged; eSign is providing the same features you are used to.
-
The signature data storage is not changing. All of your data will continue to be stored within your Atlassian Confluence cloud site.
-
eSign on Forge will be initially released as “opt-in”; your site will not receive the update until the Confluence Administrator updates the eSign app.
-
Because it is a foundational platform and technology change, we recommend that you test to ensure that your specific configuration and workflows work well, and identify where there may be some user/training impact due to the changes.
See the 2026 Change Log for all changes to eSign beyond the Forge Upgrade.
Forge Upgrade Timeline
The Forge Upgrade will proceed in phases.
|
Phase |
Description |
|---|---|
|
1. Infrastructure
|
The eSign backend service infrastructure is upgraded to support Forge platform technology. No user impact for this phase. |
|
2. Early Access
|
The new version will be released for optional update. Existing customers will not be automatically upgraded. This version may be installed in sandbox/test sites and updated to production on a per site basis during the Early Access phase. |
|
3. GA Release
|
Having been proved stable, eSign version 3 is now classified as GA and recommended for all customers. |
Applying the Upgrade
Upgrading the eSign Signatures for Confluence from V2 to V3 can be done in the Atlassian app management portal by a Site Administrator.
Upgrade Steps
-
In Confluence, access the Apps > … > Manage Apps menu.
-
In Manage Apps, click the “Take me there” button to open Connect Apps in Administration
-
In Connected apps, enter “esign” into the search box to filter for the eSign Signatures for Confluence app. Then press View app details.
-
In the App Details page for eSign Documents, verify the current version is Outdated (2.X) and then press the Update button in the top right corner to move to the update screen.
-
In the “Update to the last version” dialog, press Accept & Update to authorize the upgrade. After this point the site will be upgraded to Version 3 of eSign. It is not possible to revert back to Version 2.
-
Atlassian will popup an upgrade in progress notification and within a few minutes will report upgrade complete.
-
Return to Confluence; there will be a new Apps > Signatures Hub menu item available. Open this to confirm V3 is installed and working.
-
Navigate to any Confluence page with existing signatures and view the updated Signatures panel. It has all the same capabilities and layout is very similar to the V2 panel.
Continue exploring the new version. Review the Scope of Changes section below for a full list of all impacted screens, reports and macros.
Data Migration
This upgrade does not change any of the signature metadata stored within Confluence, no data needs to be migrated.
Scope of Changes
This section highlights the various eSign user accessible features and any functional impacts of the forge upgrade. This list may be useful in reviewing your team's usage of eSign and identifying the use cases to validate with your configuration.
All eSign screens and dialogs have been converted to the new Forge technology; there will be minor cosmetic changes to field and screens.
|
Feature / Page |
Impact |
What’s Changed |
|---|---|---|
Signature Process
|
|
|
|
Signatures Byline |
no change |
|
|
Manage Signatures |
Low |
The page title, version and updated on are now displayed on the Manage Signatures page. |
|
Signing Page Byline |
no change |
|
|
Signing Page |
no change |
|
|
Start (Open for Signatures) |
no change |
|
|
Execute Signature |
no change |
|
|
Invite to Sign |
no change |
Pending checkbox renamed to Unassigned |
|
Finalize (and Archive) |
no change |
|
|
View Signature |
no change |
|
|
Signature Admin |
Low |
Page Lock and Unlock actions added to the Administration dialog. |
|
Verification Report |
no change |
|
|
Audit Report |
no change |
|
|
|
|
|
Signature Macros
|
||
|
eSign Signature Block |
no change |
|
|
eSign Signature Tag |
no change |
|
|
eSign Signature Verification |
no change |
|
|
eSign Search |
no change |
|
|
Notes |
|
|
|
|
|
|
Signature Overview
|
||
|
Signature Hub |
Low |
The new Signature Hub is available under the global Apps menu. It expands on the previous Search Signatures page with additional view of My Invites and My Signatures, plus Search.
|
|
Signature Dashboard |
Low |
The Signature Dashboard provides space level search and visibility similar to the Signature Hub.
|
|
Signature Profile |
Low |
The Signature Profile page can be reached from the Signature Hub. The Signature Profile is not accessible from the Confluence User Profile menu as that is not supported by Forge. |
|
|
|
|
Macro Export
|
|
|
|
PDF Macro Export |
MEDIUM |
The PDF Export of macros is Improved under Forge. PDF exports of all eSign macros will now closely match what is seen on screen, including the cursive Signature font rendering of Signatures. |
|
MS Word Macro Export |
Low |
Minimal layout impact |
|
Third Party Macro Export |
Low |
Minimal layout impact |
Administration
|
|
|
|
App Configuration - Site |
Low |
Site level configuration is located under Apps > eSign Electronic Signatures within Confluence > Apps > Manage Apps. |
|
App Configuration - Space |
Low |
Space level configuration is now in Space Settings > Apps > eSign Electronic Signatures. |
|
|
|
|
Workflow Automation
|
||
|
Webhooks |
no change |
Webhooks for the following events remain available: On Start, On Invite, On Signature, and On Finalize |
|
|
|
|
Additional Items
|
|
|
|
eSign Custom Indexing |
no change |
All custom eSign indexed fields will transition to Forge automatically after upgrade. |
|
Guest Access |
no change |
Guest access to eSign on Forge is supported. |
|
Blueprints |
MEDIUM |
Atlassian Forge has removed support for Confluence Blueprints for Apps. As an alternative, any page with eSign macros can be used as a template for subsequent pages. The eSign macros and configurations will seamlessly carry forward to copied pages. Signature and audit data from the original data is not copied. |
References
For more information about the Atlassian Forge platform and transition, see: