Contents
Introduction
eSign for Confluence allows users to sign pages. Here is an example of a page that was signed by 3 different people.
Signature Workflow Stages
First locate the Page to be signed and (optionally) add Signature Tags/Block macros to it. Note that pages with Tags already in them can be copied and used as templates.
Open the page for signatures via Start.
Invite Users and wait for them to Sign.
Finalize Signatures
Signatures for each page progresses through 3 states with each page being managed by Signature Page Owners. Owners are set at the beginning of the process when Signatures are Started.
Signature Tag and Signature Block Macros
The signature tag (one signature) and signature block (multiple) macros can be added to any confluence page in any location enable on-page signatures.
Add these macros anywhere within the the Confluence page while it is open for editing by typing “/esign” and selecting eSign Signature Tag or Block from the macro pick-list. Configure the macros to select the signature meaning and display options.
Open the Page for Signatures
The user who Opens the page for Signatures for this page is by default an owner; they can optionally add additional users.
Owners can Invite and Administer signatures for the page. Space administrators can act as Owners.
The Signature Tags option is required for Signature Tags to be used within the page. Enable this unless you require the legacy behavior of Signature Blocks only.
The Signing Page (Appendix) enables collection of off-page signatures for the page. Use this when signatures should not appear within the page. The Appendix containing all signatures can be saved/printed to PDF.
eSign allows to limit pages to be signed by Invitees Only. This option can be selected on the Open Signatures dialog (Start). If selected, only users who are invited to sign will be able to execute signatures on this page. Otherwise the page is open for any logged in user with access to the page to apply a signature.
Inviting Users to Sign
Users can be “invited” to sign a page by clicking the Invite User button within the Signature Tag or Block. Users invited will receive an email with a link to the page to sign.
Single signature tags have one invitee. Signature Blocks and the Signing Page Appendix can have many active invites.
Users that have been invited to sign will receive an email and will see their name and a green Sign Here flag highlighting where they should sign when they view the page.
Executing a Signature
Click the Sign Here button to open the Execute Signature dialog. Enter the Users Signature Pin and press Execute Signature. Once authenticated, the signature will be added to the page.
View Signature
Once signed, details of the signature are available as a drill in from any Signature Tag. The View Signature dialog will show the current signature and allows actions to cancel, verify and void an individual signature.
Manage Signatures
The manage signatures panel will show the current list of invites and signatures and provide access to management functions and reports. It is accessed from the page byline or from the Signatures button in the View Signature dialog.
Use the Finalize button in this page to close and lock down signatures when all signing is complete.
Finalizing Signatures
Finalize Signatures to indicate signing is complete. Once Final, no further invites or signatures may be performed on a page.
A PDF Signature Archive with all signatures, attachments, comments and page details will be generated and attached to the page (if enabled). See PDF Signature Archives
Owners and Administrators may reopen Finalized pages if it is necessary to capture more signatures.
Signature Verification
Each signature is cryptographically locked to the confluence page version and attachments. The Signature Verification feature is available to confirm that neither the content or attachments of a page has been modified since a signature was captured. Changes to the content/attachments will “break” the signature lock and show as an unverified signature on the certificate.
If a change is required (e.g. updated document revision needs to be signed, the signees can re-sign the update page. When a signature is re-executed the previous signature is “voided” and may be reviewed in the Signature Audit Report.
Signature Verification Report
A completed Signature Report can be generated to verify signature integrity for any Confluence content page.
Signature Pin Option
To Execute an Electronic Signature, users must first log in to the Atlassian Cloud. Then (if enabled) they are required to enter a Signature Pin with each Signature. This Pin is persistent and can be used repeatedly to sign Confluence pages. The first time a user opens the signature dialog the user will have to request a new Pin (via email) before they can execute a signature.
If a Pin expires, is locked out, or is forgotten, the user can request a new one via Pin Reset. When this occurs, the eSign system will generate a random pin for that user and send it to them via e-mail. The new pin can be used for Signing immediately. The user can optionally change their own Pin in the eSign User Settings page.
Pin Security Settings
Pins are minimum 6 characters in length
Pins will lock out after 6 invalid attempts and will need to be reset
Pins will expire after 180 days
Next Steps
Access eSign Search (from Apps > eSign Electronic Signatures) or User Profile > My Signatures) to view all signed content in Confluence.
Add the eSign Search macro to a page for a custom search report.</li>
Create a new page from an eSign Blueprint. Try the Training Attendance Form or Document Approval blueprint.
Add the eSign Signature Tag or eSign Signature Block macros to any page to allow display and signing inline.
Review Change Logs - eSign for Confluence for news on recent updates.
Notes
Limit of 50 users may be invited through the Invite dialog at one time. Subsequent invite requests can add additional users to the page.