eSign for Confluence - Forge Upgrade FAQ | eSign Documentation and Support

eSign on Forge is releasing June 6, 2026 and will be available for upgrade 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 COMPLETED 2026-02	The eSign backend service infrastructure is upgraded to support Forge platform technology. No user impact for this phase.
2. Early Access IN PROGRESS June 2026	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. Site Upgrades to the Forge release are one-way and cannot be rolled back. We recommend testing in a sandbox or non-production environment first. Once the Early Access phase has started all new installations will be eSign on Forge.
3. Full Release Sept 2026	After eSign on Forge has proven stable, it will transition to Full Release.

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.

info 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	Pages with existing eSign macros will continue to work and display within the new eSign on Forge macros. Confluence will automatically convert and upgrade existing eSign macros to Forge the first time they are edited.

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. It also provides a link to the user’s Signature Profile, eSign News and User Guide.
Signature Dashboard	Low	The Signature Dashboard provides space level search and visibility similar to the Signature Hub. It is available under Space > Space Apps > Signature Dashboard or can be opened from the Search link in Manage Signatures.
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	HIGH	Forge’s Microsft Word export is not yet robust enough for production use. We are working with Atlassian on identified issues and will enable MS Word exports as soon as possible

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. We have observed the reindexing take up to 1 hour in some sites. During this time the eSign seaches in Signature Hub and Signature Dashboard may not show all pages. It is safe to continue inviting at signing at the page level while waiting for indexes.
Blueprints	HIGH	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:

https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps

Forge Upgrade Timeline

Scope of Changes

Signature Process

Signature Macros

Signature Overview

Macro Export

Administration

Workflow Automation

Additional Items

References