---
title: "Branding"
url: "https://docs.signnow.com/docs/guides-branding"
type: "page"
section: "Documentation"
slug: "guides-branding"
---

# Branding

# About branding

**Branding** (white-labeling) lets you tailor the signing, sending, and viewing experience, as well as email notifications, to match your company’s style.

SignNow allows API users to customize every step of the signer and sender journey:

- Email notifications with an invite to sign.
- How the editor looks during the signing session and when viewing the document afterward.
- How the editor looks when sending a document or document group for signing (embedded sending).
- How the editor looks in embedded editor mode.
- How the editor looks in embedded view mode.
- The **Send Invite** page for embedded sending.
- The completion page shown after signing a document.
- Other email notifications related to signing.


## Customization level

Branding can be used with a single document, document group, application, or organization.

> A signing session is an editing and viewing experience that a recipient enters when opening a document in the SignNow editor.

<table style="width:100%">
<thead>
<tr>
<th> Customization level </th> <th> What is customized </th> <th style="width:45%"> When to use </th>
</tr>
</thead>

<tr>
<td><a href="/docs/general-branding/operations/put-v2-applications-application_id-brand"><b>Application</b></a></td>
<td> Signing session for all invites, embedded sending, embedded editor, embedded view links, and emails sent within an application.</td>
<td> Use if all your invites need to look the same way. </td>
</tr>

<tr>
<td><a href="/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id"><b>Organization</b></a></td>
<td><li> Signing session for all invites, embedded sending, embedded editor, embedded view links sent by users who belong to the organization. </li><li>All emails sent regarding those invites.</li></td>
<td> Use if you need to have different groups of invites customized differently. </td>
</tr>

<tr>
<td><a href="/docs/general-branding/operations/put-v2-documents-document_id-brand"><b>Document</b></a></td>
<td><li> Signing session for document invites (field invite, embedded invite, signing link, and FreeForm invite) and emails sent regarding the invites.</li><li>Document embedded sending experience.</li><li>Document embedded editor experience.</li><li>Document embedded view experience.</li> </td>
<td><ul><li> Use to make exceptions from the application brand or organization brand. </li><li> Use to customize specific invites. </li></ul></td>
</tr>

<tr>
<td><a href="/docs/general-branding/operations/put-v2-document-groups-document_group_id-brand"><b>Document group</b></a></td>
<td><li> Signing session for document group invites (field invite, embedded invite, signing link, and FreeForm invite) and emails sent regarding the invites.</li><li>Document group embedded sending experience.</li><li>Document group embedded editor experience.</li><li>Document group embedded view experience.</td>
<td><ul><li> Use to make exceptions from the application brand or organization brand. </li><li> Use to customize specific invites. </li></ul></td>
</tr>

</table>

## Brand ownership

Each brand has an `owner_type` field that defines who owns it and what access is allowed. There are three ownership types:

| `owner_type` | Description |
|---|---|
| `common` | System default SignNow brand. Read-only — cannot be edited or customized. Appears in the brand list, but any modification attempt returns a "No access to brand" error. |
| `organization` | Custom brand owned by the organization. Full access for organization admins. This is the brand type you should create and use for customization. |
| `user` | Custom brand owned by an individual user. |

<!-- theme: warning -->
> If you receive a "No access to brand" error, check the `owner_type` of the brand via the [Get all brands](/docs/general-branding/operations/get-v2-brands) or [Get organization brands](/docs/organization-branding/operations/get-v2-organizations-organization_id-brands) endpoint. If it is `common`, the brand is read-only and cannot be edited. Create an organization or user brand instead.

## What you can customize

To customize the signing, sending, and viewing experiences, add resources to the brand. Brands consist of the following resources:

* [General resource](/docs/general-branding/operations/put-v2-brands-brand_id-general): customize the color scheme, consent text, welcome message, and help center menu option visibility of the signing session; the color scheme for the embedded editor, embedded sending, and embedded view experiences.
* [Editor resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor): customize the look of the editor, button text and visibility on the completion page, and text on the authentication page. 
* [Send Invite resource](/docs/general-branding/operations/put-v2-brands-brand_id-resources-send-invite): customize the **Send Invite** page for the embedded sending experience.
* [Logo resource](/docs/general-branding/operations/post-v2-brands-brand_id-logo): customize the logo for the signing session, completion and authentication page, embedded sending and embedded view experience.
* Email resources:
  * [Email general](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general): customize general settings of email notifications.
  * [Email logo](/docs/general-email-branding/operations/post-v2-brands-brand_id-email-logo): customize the logo that appears in the emails.
  * [Email invite](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite): customize the email text that notifies a signer that they have a pending invite.
  * [Email reassign](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite-reassign): customize the email text that notifies a new signer that an invite to sign was reassigned to them.
  * [Email canceled](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite-canceled): customize the email that notifies a signer that a sender canceled their invite.
  * [Email completed](/docs/general-email-branding/operations/put-v2-brands-brand_id-resources-email-invite-completed): customize the email that notifies a signer that their invite was completed.
  * [Email reminder](/docs/general-email-branding/operations/put-v2-brands-brand_id-resources-email-invite-reminder): customize the email that reminds a signer about a pending invite.
* CC email resources:
  * [CC email for invite](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite): customize CC emails sent with invite emails.
  * [CC email for reassign](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-reassign): customize CC emails sent with reassign emails.
  * [CC email for step completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-step-completed): customize CC emails sent when a step of an invite is completed.
  * [CC email FreeForm signed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-signed): customize CC emails sent when a FreeForm invite is signed.
  * [CC email completed](/docs/cc-email-branding/operations/put-v2-brands-brand_id-resources-email-cc-invite-completed): customize CC emails sent when an invite to sign is completed.
  
You can add the resources you need and omit those you don’t. The same applies to attributes within resources. If you don’t customize a part of the signing, sending, or viewing experience, it will use the default SignNow branding.

See the full list of attributes for each resource in its respective section.

## Branding and web settings configuration priority

SignNow resolves branding configurations based on a specific order of importance. Higher level branding configurations override lower level ones.

| Priority | Level | Scope | Notes |
| --- | --- | --- | --- |
| 1 (Highest) | Invite /Document/Document group | Specific document or group | Overrides all other branding configurations. |
| 2 | Application | API application | Overrides organization (workspace) branding. |
| 3 (Lowest) | Organization | Organization (workspace) | Applies to all organization (workspace) members.<br> **Note:** If **Disable branding setup** is enabled in **Workspace Settings,** members will be prohibited from setting up, editing, or sending invites with a custom branding. |

> Generally, API-configured branding overrides UI settings when the invite is sent via API. When the invite is sent via the SignNow web app — including via an embedded sending link — UI settings override API-configured branding. In both cases, parameters passed directly at the invite level take the highest priority, overriding both API-configured branding and UI settings.
> 

See the examples below for more details.

---

## **Example 1: Invite email subject and message with embedded sending and invite to sign**

This example shows how API-configured branding interacts with UI-configured settings depending on the sending method.

**Setup**

- Via API, an [email invite brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) is created with the email subject `Signature request from ACME company` and message `Please review and sign the contract from ACME company`, and assigned to the document group.

**Request example**

```bash
curl --request PUT \ 
--url https://api.signnow.com/v2/brands/{{brand_id}}/resources/email-invite \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
    "en": {
        "subject": "Signature request from ACME company",
        "body_header": "Review and sign the contract",
        "body_message": "Please review and sign the contract from ACME company"
    }
}'
```

- Via the SignNow web app, the user has set a custom email subject `Urgent: Signature Required` and message `Invoice needs your signature` in **Account Settings > Default Invite Settings**.

**Scenario 1: Embedded sending**

The user creates an embedded sending link for the document group with email branding configured via API.

**Result**

The embedded sending link opens the **Send Invite** page with the pre-filled email subject: `Urgent: Signature Required` and message: `Invoice needs your signature`.

The UI invite settings override the API-configured branding.

**Scenario 2: API invite to sign / embedded signing**

The user sends the document group for signature via API or creates an embedded signing link.

**A.** The user passes the `subject:Review and sign documents` and `message: Please contact for any questions`  parameters in the request.

**Request example**

```bash
curl -- request POST \
--url https://api.signnow.com/documentgroup/{{document_group_id}}/groupinvite \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "invite_steps": [
        {
            "order": 1,
            "invite_emails": [
                {
                    "email": "recipient@email.com",
                    "subject": "Review and sign documents",
                    "message": "Please contact for any questions"
                }
            ],
            "invite_actions": [
                {
                    "email": "recipient@email.com",
                    "role_name": "Recipient 1",
                    "action": "sign",
                    "document_id": "XXXXX61886d64cbcb308d22a14fb7378ad1081ba"
                }
            ]
        }
    ]
}'
```

**Result A**

The recipient receives an invite email with the subject `Review and sign documents` and message `Please contact for any questions`.

The invite-level parameters passed directly in the API request override both API-configured branding and UI invite settings.

**B.** The user does not pass `subject` and `message` parameters in the request.

**Result B**

The recipient receives an invite email with the subject `Signature request from ACME company` and message `Please review and sign the contract from ACME company`.

The API-configured branding overrides the UI invite settings.

---

## **Example 2: `from_name` and `from_email` with embedded sending and embedded signing**

This example shows how API-configured branding interacts with UI-configured settings for `from_name` and `from_email` in embedded sending and embedded signing.

The following priority order applies specifically to the sender's name and email address. It provides a more granular breakdown within the broader priority framework described above:

1. `from_name` / `from_email`
2. Invite settings
3. Branding at document, document group, or application level
4. Generic
5. Branding at organization (workspace) level

**Setup**

- Via API, an email invite brand resource is created with `from: John Smith` and assigned to the document group.

**Request example**

```bash
curl --location --request PUT 'https://api.signnow.com/v2/brands/{{brand_id}}/resources/email-invite' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
    "en": {
        "subject": "Signature request from ACME company",
        "body_header": "Review and sign the contract",
        "body_message": "Please review and sign the contract from ACME company",
        "from": "John Smith"
    }
}'
```

- Via the SignNow web app, the user has set a custom email subject `Urgent: Signature Request from {Sender name}` in **Account Settings > Default Invite Settings**. `{Sender name}` will be replaced by `Anna Green`.

**Scenario 1: Embedded sending**

The user creates an embedded sending link for the document group with email branding configured via API and passes the `from_name: Michael Stone` parameter.

**Result**

The embedded sending link opens the **Send Invite** page with the pre-filled email subject: `Urgent: Signature Request from Michael Stone`.

Regarding the sender name: the `from_name` parameter overrides both the API-configured branding (`John Smith`) and the UI invite settings (`Anna Green`).

Regarding the email subject and message: the UI invite settings override the API-configured subject and message in the email invite brand resource.

See also: [other scenarios](/docs/guides-embedded-signing#senders-email-address-and-name) of passing `from_name` and `from_email` for embedded sending.

**Scenario 2: Embedded signing**

The user creates an embedded signing link for the document group and passes the `from_name: Michael Stone` parameter (`delivery_type=email`). 

**Result**

The recipient receives an invite email with `from: Michael Stone`, email subject `Signature request from ACME company`, and email message `Please review and sign the contract from ACME company`.

Regarding the sender name: the `from_name` parameter overrides both the API-configured branding (`John Smith`) and the UI invite settings (`Anna Green`).

Regarding the email subject and message: the API-configured email invite branding overrides the UI invite settings.

See also: [other scenarios](/docs/guides-embedded-signing#senders-email-address-and-name) of passing `from_name` and `from_email` for embedded signing.

> To reset the invite email message and subject in the web app:
> 
> 1. Go to https://app.signnow.com/webapp/my-account/settings
> 2. Locate the **Default Invite Settings** section.
> 3. Next to the **Invite Email Subject** or **Invite Email Message** setting, click **Change**.
> 4. In the panel that opens, click **Reset to Default**.

---

### Configuration matrix

The table below details customizable items at each level and the specific API or web paths to configure them.

| Feature | Organization (workspace) | Application | Invite / Document / Document group | Account Settings |
|---|---|---|---|---|
| Add/Change logo | **API:** [Org logo brand resource](/docs/organization-branding/operations/post-v2-organizations-organization_id-brands-brand_id-resources-logo)<br>**Web:** Workspace Settings > Workspace logo | **API:** [Logo brand resource](/docs/general-branding/operations/post-v2-brands-brand_id-logo) | **API:** [Logo brand resource](/docs/general-branding/operations/post-v2-brands-brand_id-logo)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Auto-apply signature and initials | **API:** `auto-apply-signatures-and-initials-to-document-fields` parameter in [Org editor brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-editor)<br>**Web:** Workspace Settings > Signing Settings | **API:** `auto-apply-signatures-and-initials-to-document-fields` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | **API:** `auto-apply-signatures-and-initials-to-document-fields` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | |
| Hide **Decline to Sign** | **API:** `decline-button` parameter in [Org editor brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-editor)<br>**Web:** Workspace Settings > Signing Settings | **API:** `decline-button` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | **API:**<br>• `decline-button` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor)<br>• `decline_by_signature` in API invite requests | |
| Guide signers through fields | **API:** `guide-signers-only-through-required-fields` parameter in [Org editor brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-editor)<br>**Web:** Workspace Settings > Signing Settings | **API:** `guide-signers-only-through-required-fields` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | **API:** `guide-signers-only-through-required-fields` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | |
| Set button colors for signing session | **API:** `buttons.primary.color` and `texts.color` parameters in [Org general brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-general)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `buttons.primary.color` and `texts.color` parameters in [General brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-general) | **API:** `buttons.primary.color` and `texts.color` parameters in [General brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-general)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Set header colors for signing session | **API:** <br>•`header.background`, `texts.color`, `icons` parameters in [Org general brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-general) <br>•`progress-bar` object in [Org editor brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-editor)<br>**Web:** Workspace Settings > Branding and Customization | **API:** <br>•`header.background`, `texts.color`, `icons` parameters in [General brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-general) <br>•`progress-bar` object in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) | **API:** <br>•`header.background`, `texts.color`, `icons` parameters in [General brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-general) <br>•`progress-bar` object in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Set recipient redirects | **Web:** Workspace Settings > Redirect recipients |  | **API:**<br>• `redirect` parameters in API invite requests<br>**Web:** On the **Send Invite** page > More > Advanced Options > Actions On Completion | |
| Document completion attachments | **Web:** Workspace Settings > Email Settings |  | **Web:** On the **Send Invite** page > More > Advanced Options > Actions On Completion | |
| Disable payment request setup | **API:** `request-payment` parameter in [Org editor brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-editor)<br>**Web:** Workspace Settings > Additional Settings > Disable payment request setup | **API:** `request-payment` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) or [Send Invite brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-resources-send-invite) | **API:** `request-payment` parameter in [Editor brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-editor) or [Send Invite brand resource](/docs/general-branding/operations/put-v2-brands-brand_id-resources-send-invite) | |
| Add email logo | **Web:** Workspace Settings > Branding and Customization | **API:** [Email logo brand resource](/docs/general-email-branding/operations/post-v2-brands-brand_id-email-logo) | **API:** [Email logo brand resource](/docs/general-email-branding/operations/post-v2-brands-brand_id-email-logo)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Logo position | **API:** `logo.position` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `logo.position` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general) | **API:** `logo.position` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Button colors | **API:** `buttons` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `buttons` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general) | **API:** `buttons` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Email headline | **API:** `body_header` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `body_header` parameter in [Invite email brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) | **API:** `body_header` parameter in [Invite email brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Subject and message | **API:** `subject`, `body_message` parameters in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `subject`, `body_message` parameters in [Invite email brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) | **API:**<br>• `subject`, `body_message` parameters in [Invite email brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite)<br>• `subject`, `message` parameters in API invite requests<br>**Web:**<br>• On the **Send Invite** page > Branding Theme<br>• On the **Send Invite** page > Customize Message | **Web:** Account Settings > Default Invite Settings |
| Sender email (Reply-to) | **API:** `sender_email` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `sender_email` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general) | **API:**<br>• `sender_email` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general)<br>• `from_email` parameter in embedded sending or embedded signing requests<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Sender name | **API:** `from` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `from` parameter in [Email invite brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) | **API:**<br>• `from_name` parameter in embedded sending or embedded signing requests<br>• `from` parameter in [Email invite brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) | **Web:** Account Settings > Default Invite Settings |
| Footer text | **API:** `footer_message` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `footer_message` parameter in [Email invite brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite) | **API:** `footer_message` parameter in [Email invite brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-invite)<br>**Web:** On the **Send Invite** page > Branding Theme | |
| Remove SignNow references | **API:** `signnow_references` parameter in [Org email brand resource](/docs/organization-branding/operations/put-v2-organizations-organization_id-brands-brand_id-resources-email)<br>**Web:** Workspace Settings > Branding and Customization | **API:** `signnow_references` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general) | **API:** `signnow_references` parameter in [Email general brand resource](/docs/general-email-branding/operations/put-v2-brands-brand_id_1-resources-email-general)<br>**Web:** On the **Send Invite** page > Branding Theme | |


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