E-Signatures

Overview

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

Each approval must be configured to require user authentication.

The workflow popup contains 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 is only 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 the global configuration for e-signature is set to require 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 the global configuration for e-signature is set to require the use of a signing token the credentials prompt in the workflow popup is either

  • the user's Confluence username and the signing token

  • the signing token

If a signing token is required, a user needs to undertake a one-time set up an authentication app before undertaking an approval. The authentication app is then used to generate a time-based signing token required for each approval.

Related Links

User Guide

Authoring Guide

Confluence Administration