---
title: "Email and CC email resources"
url: "https://docs.signnow.com/docs/branding-email-resources"
type: "page"
section: "Documentation"
slug: "branding-email-resources"
---

# Email and CC email resources

# Email resources and CC email resources

## Email resources

![email example.png](/reference-assets/images/Branding%20guide/Email/email%20example.png)

![mobile references and download instructions.png](/reference-assets/images/Branding%20guide/Email/mobile%20references%20and%20download%20instructions.png)

![email_general_new.png](/reference-assets/images/Branding%20guide/Email/email_general_new.png)

### Email general 

All these elements are customizable for every email or email type. These include an email invitation to sign a document or an email about the completion of a document. You can also add texts in three languages: English, Spanish, and French.

> These resources allow the branding of primary emails. For CC email branding, see [CC email resources](/docs/guides-branding#cc-email-resources).

<table style="width:100%">
<thead>
<tr>
<th> UI element </th> <th> Customization options </th> <th style="width:45%"> Attributes with values </th>
</tr>
</thead>
<tr>
<td>Logo</td>
<td>Logo position. Possible values: left, middle, or right</td>
<td>
    
```json
"logo": {
  "position": "middle"
}
```

</td>
</tr>
<tr>
<td>View Document button</td>
<td>The text color and background color of the button</td>
<td>
    
```json
"buttons": {
  "color": "#38424b",
  "background": "#e3e6e9"
}
```

</td>
</tr>
<tr>
<td>Contact Sender button</td>
<td>The text color and background color of the button</td>
<td>
    
```json
"secondary_buttons": {
  "color": "#38424b",
  "background": "#e3e6e9"
}
```

</td>
</tr>
<tr>
<td>Sender email</td>
<td>An email address preset for an email draft that opens when a signer clicks the Contact Sender button</td>
<td>
    
```json
"sender_email": "sender@email.com"
```

</td>
</tr>
<tr>
<td>Links to SignNow mobile apps</td>
<td>Hide or show the links to SignNow mobile apps at the bottom of the email</td>
<td>
    
```json
"signnow_references": true
```

</td>
</tr>
<tr>
<td>Instructions on how to download the completed document</td>
<td>Hide or show the instructions on how to download the completed document</td>
<td>
    
```json
"hide_download_image": true
```

</td>
</tr>
</td>
</tr>
<tr>
<td>Contact Sender section</td>
<td>Hide or show the Contact Sender section in the emails</td>
<td>

```json
"contact_sender": {
  "visibility": false
}
```
</td>
</tr>
<tr>
<td>CCD section</td>
<td>Hide or show the list of CCD emails in the invite emails</td>
<td>

```json
"ccd": {
  "visibility": false
}
```
</td>
</tr>
</table>
</table>

### Email logo

Update the logo on the emails. There are two ways to customize a logo:

* By [uploading](/docs/general-email-branding/operations/post-v2-brands-brand_id-email-logo) an image from your computer.

```bash
curl --request POST \
  --url https://api.signnow.com/v2/brands/brand_id/resources/email-logo \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer {{access_token}}' \
  --header 'Content-Type: multipart/form-data' \
  --form 'logo=@"/path/to/file"'
```

* By [uploading](/docs/general-email-branding/operations/put-v2-brands-brand_id-resources-email-logo) an image from a URL.

```bash
curl --request PUT \
  --url https://api.signnow.com/v2/brands/brand_id/resources/email-logo \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer {{access_token}}' \
  --header 'Content-Type: application/json' \
  --data '{
  "url": "https://logo-file.com"
}'
```

The logo on the signing session and completion page can be customized using the [logo resource](/docs/general-branding/operations/post-v2-brands-brand_id-logo).

### Email invite, reassign, canceled, completed, and reminder resources

<table style="width:100%">
<thead>
<tr>
<th style="width:25%">Resources</th><th>UI element</th><th style="width:30%">Customization options</th><th>Attributes with values</th>
</tr>
</thead>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Language</td>
<td>You can set texts in English, Spanish, and French. The texts need to be translated before adding to the branding resource. For more information, see <a href="/docs/guides-branding#language-branding">Language branding</a>.</td>
<td>

```json
"en": {
  "subject": "Needs your signature",
  "body_header": "You were invited to review and sign a document"
},
"fr": {
  "subject": "A besoin de votre signature",
  "body_header": "Vous avez été invité à vérifier et signer un document"
},
"es": {
  "subject": "Necesita tu firma",
  "body_header": "Te han invitado a revisar y firmar un documento"
}

```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Subject</td>
<td>Custom subject text up to 300 symbols. Placeholder {document_name} is available</td>
<td>

```json
"en": {
  "subject": "My custom subject {document_name}"
}
```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Body header</td>
<td>Custom email header text up to 300 symbols</td>
<td>

```json
"en": {
  "body_header": "Body header message"
}
```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Body message</td>
<td>Custom email body text up to 300 symbols. Placeholder {document_name} is available</td>
<td>

```json
"en": {
  "body_message": "Body message {document_name}"
}
```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Footer message</td>
<td>Custom email footer text up to 300 symbols</td>
<td>

```json
"en": {
  "footer_message": "Footer message"
}
```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Canceled</li>
  <li>Completed</li>
  <li>Reminder</li>
</td>
<td>Sender</td>
<td>Custom text indicating sender up to 300 symbols</td>
<td>

```json
"en": {
  "from": "From user user@mail.com"
}
```

</td>
</tr>
<tr>
<td>
  <li>Invite</li>
  <li>Reassign</li>
  <li>Reminder</li>
</td>
<td>Expiration message</td>
<td>Custom text about email expiration up to 300 symbols. Placeholder {days} is available: data from the invite expiration_days parameter is used</td>
<td>

```json
"en": {
  "expiration": "Expiration message {days}"
}
```

</td>
</tr>
<tr>
<td>Reassign</td>
<td>Forward message</td>
<td>Email message from a signer who forwarded the invite up to 300 symbols. Placeholder {email_from} is available</td>
<td>

```json
"en": {
  "forward_message": "Forward message {email_from}"
}
```

</td>
</tr>
</table>

### Language branding

SignNow supports three languages for email notifications: English, Spanish, and French. The language is determined by the `language` parameter in the [Document field invite](/docs/document-field-invite/operations/post-field_invite) payload. If the parameter is not set and for other invite types, the language is determined by the language of the sender's SignNow account.

Default email notifications are automatically sent in the needed language. However, if you are branding your notifications, you need to add the translated texts.

**Payload example for the email-invite brand resource**

```json

{
      "en": {
        "subject": "Needs your signature",
        "body_header": "You were invited to review and sign a document",
        "body_message": "You've been invited to fill out and sign the {document_name} document.",
        "expiration": "This invite will expire in {days} days"
      },
      "fr": {
        "subject": "A besoin de votre signature",
        "body_header": "Vous avez été invité à vérifier et signer un document",
        "body_message": "Vous invite à compléter et signer le document {document_name}.",
        "expiration": "Cette invitation expirera dans {days} jours"
      },
      "es": {
        "subject": "Necesita tu firma",
        "body_header": "Te han invitado a revisar y firmar un documento",
        "body_message": "Has invitado para rellenar y firmar el documento {document_name}.",
        "expiration": "Esta invitación dejará de ser válida en {days} días"
      }
    }

```

If you assign a brand with this resource to a document and then send a field invite for this document with `language=es`, the email invitation will contain Spanish texts.

## CC email resources
You can brand CC emails separately from the primary emails. The following CC emails can be customized for certain invite types:

| Email type | Description | Invite types |
|------------|-------------|--------------|
| [Invite CC email](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite) | Customize CC emails that are sent with invite emails. | <li>[Document field invite](/docs/document-field-invite/operations/post-field_invite)</li><li>[Document group field invite](/docs/doc-group-field-invite/operations/invite-to-sign-document-group)</li><li>[Document freeform invite](/docs/document-field-invite/operations/post-field_invite)</li> <li>[Document group freeform invite](/docs/doc-group-freeform-invite/operations/post-v2-document-groups-document_group_id-free-form-invites)</li> |
| [Reassign CC email](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-reassign) | Customize CC emails that are sent with reassign emails. | <li>[Document field invite](/docs/document-field-invite/operations/post-field_invite)</li><li>[Document group field invite](/docs/doc-group-field-invite/operations/invite-to-sign-document-group)</li> |
| [Step completed CC email](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-step-completed) | Customize CC emails that are sent when a step of an invite is completed. | [Document field invite](/docs/document-field-invite/operations/post-field_invite) |
| [Freeform signed CC email](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed) | Customize CC emails that are sent when a freeform invite is signed. If an invite has multiple signers, the CC email is sent every time a document or document group is signed. | <li>[Document freeform invite](/docs/document-field-invite/operations/post-field_invite)</li><li>[Document group freeform invite](/docs/doc-group-freeform-invite/operations/post-v2-document-groups-document_group_id-free-form-invites)</li> |
| [Invite completed CC email](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-completed) | Customize CC emails that are sent when an invite to sign is completed. | <li>[Document field invite](/docs/document-field-invite/operations/post-field_invite)</li><li>[Document group field invite](/docs/doc-group-field-invite/operations/invite-to-sign-document-group)</li><li>[Document freeform invite](/docs/document-field-invite/operations/post-field_invite)</li><li>[Document group freeform invite](/docs/doc-group-freeform-invite/operations/post-v2-document-groups-document_group_id-free-form-invites)</li> |

### Customizable elements

For all CC emails, you can customize the following email elements:

<table style="width:100%">
<thead>
<tr>
<th>Element </th><th>Description</th><th style="width:45%">Example</th>
</tr>
</thead>
<tr>
<td>Language</td>
<td>You can set texts in English, Spanish, and French. The texts need to be translated before adding to the branding resource. For more information, see <a href="/docs/guides-branding#language-branding">Language branding</a>. </td>
<td>
    
```json
"en": {
  "subject": "Needs your signature"
},
"fr": {
  "subject": "A besoin de votre signature"
},
"es": {
  "subject": "Necesita tu firma"
}
```
</td>
</tr>
<tr>
<td>Subject</td>
<td>Custom subject text up to 300 symbols. The following placeholders are available:<br>

`{sender_email}`
- [Invite](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite) CC emails<br>
- [Reassign](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-reassign) CC emails

`{document_name}`<br>
- [step completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-step-completed) CC emails<br>
- [invite completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-completed) CC emails

`{signer_email}` for [freeform signed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed) CC emails.</td>
<td>
    
```json
"en": {
  "subject": "My custom subject {document_name}"
}
```
</td>
</tr>
<tr>
<td>Body header</td>
<td>Custom email header text up to 300 symbols. The following placeholders are available:<br>

`{sender_email}` for [invite](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite) CC emails


`{step_number}` for [step completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-step-completed) CC emails


`{signer_email}` for [freeform signed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed) CC emails


`{document name}` for [invite completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-completed) CC emails</td>

<td>
    
```json
"en": {
  "body_header": "Body header message {sender_email}"
}
```
</td>
</tr>
<tr>
<td>Body message</td>
<td>Custom email body text up to 300 symbols. The following placeholders are available:<br>

`{sender_email}` and `{document_name}`<br> 
- [Invite](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite)
- [Reassign](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-reassign)
- [Freeform signed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed)
- [Invite completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-completed)


`{signer_email}` 
- [Invite](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite)
- [Freeform signed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed)


`{step_number}` for [step completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-step-completed) CC emails


`{old_signer_email}` and `{new_signer_email}` for [reassign](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-reassign) CC emails</td>
<td>
    
```json
"en": {
  "body_message": "Body message {document_name}"
}
```
</td>
</tr>
<tr>
<td>Footer message</td>
<td>Custom email footer text up to 300 symbols.</td>
<td>
    
```json
"en": {
  "footer_message": "Footer message"
}
```
</td>
</tr>
<tr>
<td>Sender</td>
<td>Custom text indicating sender up to 300 symbols.</td>
<td>
    
```json
"en": {
  "from": "From user user@mail.com"
}
```
</td>
</tr>
<tr>
<td>CC message</td>
<td>Custom CC message text up to 300 symbols. Placeholder `{cc_emails}` is available. It lists other recipients of CC emails and can be used with all types of CC emails.</td>
<td>
    
```json
"en": {
  "ccd_message": "CC message {cc_emails}
}
```
</td>
</tr>
</table>


---
*Full page: https://docs.signnow.com/docs/branding-email-resources*