E-Signature
Overview
Each individual approval in the workflow can be configured to require reviewer identity authentication.
This adds a credentials prompt for a reviewer to the workflow popup for the individual approval.
Global administrators can choose the authentication method to be used for the approvals in the workflow.
The required credentials for authentication can be configured to be one of the following:
Confluence username and password
time-based signing token
Confluence username and password
E-signature for an approval can be set by global admin to require a reviewer to authenticate their identity by entering their Confluence username and password.
The approval decision buttons are disabled until the reviewer adds the requested credentials to the workflow popup.
This can be:
the Confluence password for each user approval decision
the Confluence username and a password for each user approval decision
Entering the credentials will activate the Approve and Reject decision buttons. The credentials are validated when the reviewer makes their approval decision.
Signing Token
E-signature for an approval can be set by global admin to require a reviewer to authenticate their identity by entering their Confluence username and a time-based signing token.
The signing token is a time-based one-time password generated by a third-party app. The app must be set up by the user for the instance.
The approval decision buttons are disabled until the reviewer adds the requested credentials to the workflow popup.
This can be: