---
title: "Signatures"
canonical: "https://support.appfire.com/space/CT/147915039/Signatures"
format: markdown
---
You can set **automatic**, **customizable** signatures with templates

- Share** one global template** for all users in all projects
- Define **per-project signatures** - to be used by all users in a given project
- Let users use **Personal** templates – defined by themselves
- Use signatures in "**Replies to customer**" in **Jira Service Management** projects only

...and more!  


> Macro (widget)

  
Look for Canned Responses and **Signatures settings** in your **project sidebar**:

![image](media://b2e13bad-ad3e-4def-9c7c-1942e59345db)


## **Cascading signature settings**  


**Signature templates** can be defined on **three levels** of **settings.**

| **Settings level** | **Personal** | **Project** | **Global** |
| --- | --- | --- | --- |
| **Available options** | 1. Use default template  
<span style="color: #7a869a">(inherit </span>*<span style="color: #7a869a">Project</span>*<span style="color: #7a869a"> template)</span>
2. Use custom *personal* template
3. Disable signatures | 1. Use default template  
<span style="color: #7a869a">(inherit </span>*<span style="color: #7a869a">Global</span>*<span style="color: #7a869a"> template)</span>
2. Use custom *project* template
3. Disable signatures | 1. Use Global template
2. Disable signatures |

The settings influence which (if any) template will be selected as a signature.

**Example**

Selecting signature for new comment by user ***Jane Doe*** from ***Acme Inc.*** in ***Project ABC***:

![image](media://0873c5e9-540e-4e2c-aae5-3dbb34365f1c)

## > Macro (anchor)

**Dynamic Variable for signatures**

Shared signatures (global or per project) can be customized to include pieces of dynamic data – by using dynamic variables.

### $personalSignatureData$

Each user can set their personal piece of information which will be included in shared templates (global or per project).  
Each organization can advise their members to provide specific information, e.g. – their first and last name, phone number etc.  
If user will not provide their data – the variable will default to their Jira display name.

### $projectSignatureData$

Project admins can also provide project-specific information, like support department name, dedicated phone number etc.

### $globalSignature$

Global signature can be used to store generic information, e.g. legal notes. Then it can be used as a part of personal and project signatures with a variable.


**Example**

If user's **personal data** will include:

![image](media://f71c1497-186a-464e-9c7d-e91d38d4e364)

and **project data** will include:

![image](media://4d4bb4be-6b02-480a-a00c-9598f7fe552f)

and **global signature** will be:

![image](media://82598da9-f544-4ae0-9766-2b3e795fe0f2)

The **resulting signature** will render as follows:

![image](media://383c7869-f637-4f1b-8855-6a38d5680b0e)

## **We're looking for feedback!**

We plan to iterate and improve the Signatures functionality.  
Your [feedback and suggestions](https://apps.appf.re/crt/support/cloud/signaturesfeedback) will be much appreciated!