---
title: "E-Signatures Configuration - Global"
canonical: "https://support.appfire.com/space/CDML/650347320/E-Signatures%20Configuration%20-%20Global"
format: markdown
---
> Macro (aura-html)


|  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
| [Global Workflows](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649530159) | [Import Workflows](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649857980) | [Configuration](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649889951) | [Notifications](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649530054) | [Audit Log](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650347726) | [Advanced Configuration](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649529530) | **E-Signatures** | [Migration Assistant](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649562633) |

<span style="color: #808080">Screen Location: </span>[Confluence Administration](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650150846)<span style="color: #808080"> → Comala Document Management section → E-Signatures</span>

## Overview

This screen allows [Confluence Admins](https://appfire.atlassian.net/wiki/spaces/CDML/pages/650150846) to set the **E-Signature Configuration** option for workflow approvals. 

![image](media://fa860b64-a7b4-48bf-a5fa-ddcf25b1fd76)

Each individual approval in a workflow can be edited to require [user authentication](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649890845). The global administrator specifies the type of authentication method that will be used.

Configuring [e-signatures](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649757622) to use a signing token is compatible with SSO use for an instance.

## User Signing Token Management

An individual user must set up an [authentication app](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649693211) to generate time-based signing tokens - time-based one-time passwords (OTP). 

Each user who has [set up a signing token app for the instance](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649760336) will be listed in the global **E-Signature Configuration** screen.

![image](media://b0d9b361-ccd2-4851-83e9-88a1cd74fc18)

  
Users with active signing tokens will only be displayed when the requirement for the use of a signing token for identity authentication is set for the instance.

A global administrator can

- **Remove** an existing user signing token. This requires the user to re-initialize the authentication app for the instance
- **Change Expiry** date for the user's signing token. This requires the user to re-initialize the authentication app for the instance when the expiration date is reached

If a user's signing token expiration date is reached the user will continue to be listed in the global **E-Signatures Configuration** screen with the expired date displayed. The user will be displayed *only until* they next <span style="color: #172b4d">open an approval.</span>

After the user logs in, they will need to re-initialize the signing token using an authentication app.

> ℹ️ ### Credentials Security
> ℹ️ 
> ℹ️ The e-signature process will submit the username and approval signing token through Comalatech's secure server without storing these details.
> ℹ️ 
> ℹ️ <span style="color: #172b4d">For usability, user validation for the credentials is provided against previous, current and the next calculated signing token generated by the authenticator app.</span>