---
title: "Signature management"
canonical: "https://support.appfire.com/space/ESF/2081325257/Signature%20management"
format: markdown
---
> Macro (aura-html)

Post functions execute automatically after a workflow transition completes, enabling you to perform actions like clearing signatures or sending notifications. Unlike validators, which prevent transitions from occurring, post functions trigger once the transition has successfully taken place, making them ideal for cleanup tasks and automated communications.

> ℹ️ **Project type limitation**  
> ℹ️ The workflow configuration capabilities described in this section can only be applied to **company-managed projects**. Team-managed projects have different workflow management capabilities and might not support all Electronic Signatures validators and post functions due to current Jira Cloud limitations.

## How to revoke E-Signatures

In multi-stage approval processes, you might need to invalidate previous signatures when an issue moves to a new phase that requires fresh authorization or when significant changes occur that affect the original approval context. The **Revoke E-Signatures** post function lets you clear signature records at specific transition points, ensuring users must sign again before proceeding to the next stage. This gives you granular control over exactly when signatures get revoked in your workflow.

When configured, this post function operates in the following way:

- Clears signature requirements for the current workflow state.
- Preserves signature history in the E-Signatures tab and issue view.
- Requires new signatures for subsequent transitions.
- Signatures appear in a different format (grayed out) to indicate they've been reset.

### Procedure

To add the **Revoke E-Signatures** post-function to a workflow transition, do this:

1. Navigate to **Project Settings **>** Workflows**.
2. Select a relevant workflow and open it for editing in **Diagram** view.
3. Select the transition that requires signature clearing.  
Typically, these are transitions that move issues to new approval phases or when significant changes occur.
4. In the options panel, click **Post Functions**.
5. Click **Add post function**.
6. Select the **Revoke E-Signatures** option and click **Add**.
7. Click **Add** to save the validator.
8. Publish the modified workflow.

---

## How to send email notifications for signature requests

In collaborative workflows where multiple stakeholders need to provide signatures, manual coordination can become a bottleneck that delays project progress. Rather than relying on manual communication or hoping users check issues regularly, you can automate the notification process to ensure timely signatures. The **ES Email Issue** post function automatically notifies users when their signatures are required.

> ✅ **Best practice:** Configure this post function one transition before the E-Signatures validator to give users advance notice.

When configured, this post function operates in the following way:

- Sends notifications to all group members until the minimum signature count is reached.
- Stops sending emails once the signature threshold is met.
- Email templates are fully customizable. You can modify the subject line and message content to match your organization's communication standards and provide clear context for signature requirements.

### Before you start

- Create a Jira user group and add all necessary users (required signers) to this group before configuring the post function.

### Procedure

To add the **ES Email Issue** post-function to a workflow transition, do this:

1. Navigate to **Project Settings **>** Workflows**.
2. Select a relevant workflow and open it for editing in **Diagram** view.
3. Select the transition that requires signature request notifications.  
Typically, this is one transition before signature validation.
4. In the options panel, click **Post Functions**.
5. Click **Add post function**.
6. Select the **ES Email Issue** and click **Add**.
7. Configure the required parameters for the post function:
  1. Select the group of users that contains the required signers.
  2. Set the threshold for sending notifications.  
Emails will be sent to all group members until this number of signatures is collected. Once the threshold is reached, no additional notification emails will be sent for this transition.
  3. Modify the email subject and body template as needed.
8. Click **Add** to save the validator.
9. Publish the modified workflow.

### Example

Let’s say your group of required signers contains 3 users. If you define the threshold for sending notifications to 1, and someone in the group has already signed the issue in the previous statuses, no one will receive an email. If you define the threshold to 3, all users will receive an email, even if there are signatures from one or two users in the group.