This site has moved to the integrated Appfire documentation and information site for our apps.
From February 2024 this site is no longer updated.
Take a look here! If you have any questions please email support@appfire.com
Using a signing token to undertake the In Approval state content review
Use a signing token to activate the content review
The workflow popup for the In Approval state content review will display a credentials option for a Token.
Add your username and the 6-digit signing token generated by the authenticator app.
The Approve and Reject buttons become active when a signing token and username are added.
The credentials are validated when the user undertakes the approval decision.
- the signing token is valid for a limited time and may not be valid if you take too long to make your decision.
- each user will need to set up and use a separate signing token.
- each content review in the workflow will require a signing token.
An invalid credentials screen message will be displayed if the username added has no valid signing token set up or the signing token code is incorrect or exceeded its time-based validity.
A global administrator must have configured the global e-signature to use a Signing Token. The default e-signature configuration credentials required for the In Approval state content review are the Confluence username and password for each assigned reviewer.
The workflow popup will display a link to the personal set up and validation of the app for the user in the instance if the assigned reviewer has not set up an authenticator app to generate the signing token.