Authentication apps

Set up an approval signing token

If e-signatures are globally configured to require a signing token then a first-time user will be asked to set up an identity authentication app when they first open the workflow popup for the In Approval state.

Choose setup a personal code prompt in the workflow popup to open the Signing Token screen for the user.

The initial Signing Token screen will display instructions to add a user account to an authentication app.

Users can also access the Signing Token screen through their user profile or the Signing Token option in the page tools menu.

Add the authentication app to your smart device

Download and install a authentication app through your device/desktop app store. Here are some possible examples

• Android: Authy, Google Authenticator, 1Password, Microsoft Authenticator
• iPhone: Authy, Google Authenticator, 1Password, Microsoft Authenticator

A number of authenticator apps are also available for desktop (such as Authy).

You may already have an app installed if you have identity authentication for other applications or internet sites.

If you are already using an authentication app for Confluence login, this will not be the same account.

A new authentication account will need to be added to the app that is just used for Comala Document Control approvals.

The app will simply set up a user account that is specific to the current Confluence instance. 

• this is a one time set up for each user.
• once set up the app can be used repeatedly to generate time-based tokens for reviewer authentication.
• users accessing multiple instances will be required to set up an account for each instance.

A global administrator can reset the signing token for each user and can change the expiry date for the user signing token.