Using an Approval Signing Token to activate a review

Using an approval signing token to activate a review in the Quality Management Systems workflow

You must have previously successfully initialized the signing token for the current Confluence instance using an authenticator app.

Adding user authentication

In a state in the Quality Management Systems workflow with a content review

  • open the workflow popup

  • add your email address

  • add the authenticator app time-based signing token displayed on your smart device

cdcc_approvalpopup_esignature_email_token_elle.png

If the signing token and email are accepted, the popup content review buttons become active for that user.

A different approval signing token generated by the authenticator may be required for this content review if more than one minute has elapsed since the last use of the token.

When a valid signing token and email address are added, the review buttons are activated.

cdcc_qms_inapproval_esign_elle.png
  • for usability, user validation is provided against previous, current, and next calculated signing tokens generated by the authenticator app

  • the e-signature process submits the user email address and approval signing token through Appfire Comala secure server without storing these details

E-signature does not work if your site is configured to use a single sign-on (SSO) through Atlassian Access

Where there are multiple reviewers, a separate approval signing token is required by each reviewer.

Related Links