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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Related Pages

Overview

The e-signature feature allows workflow authors to require that users authenticate their identity to activate and undertake an approval.

  • the approval must be configured to require user authentication.

The workflow popup will contain a credentials prompt for the user.

Global administrators can set the authentication process to be based on either the Confluence username and password or a signing token generated by a third party authentication app.

Workflow authors can configure each approval to require user credentials.

Global configuration of credentials required for a reviewer

E-signature credentials required for approvals in the workflow can be configured globally to use either:

  • the user's Confluence username and password.
  • the user's Confluence username and a signing token generated by a third-party app.

This is configured in the global Comala Document Management E-Signatures Configuration screen.


 User authentication will only be requested for an approval configured to require reviewer credentials.

If Signing Token is selected:


Editing an approval to require credentials for a reviewer

Each approval can be edited using workflow builder to set the requirement for the submission of credentials by a reviewer to activate and undertake the approval.


The approval can be configured to require the credentials submitted in the workflow popup as one of the following:

  • no user authentication
  • password authentication
  • username and password authentication


If global configuration for e-signature is set for the use of the user's Confluence username and password the credentials prompt in the workflow popup will be either:

  • the user's Confluence username and the user's Confluence password
  • the user's Confluence password


If global configuration for e-signature is set for the use of a signing token the credentials prompt in the workflow popup will be either:

  • the user's Confluence username and the signing token
  • the signing token

If a signing token is required the first time user will need to set up an authentication app.

The authentication app can then be used to generate a time-based signing token required for each approval.

  • No labels