Outcome
The enabled signature preview matches the sanitized content that hosted messages will append.
Navigation path
Settings > Email sending > Email signature
Access
Active CREBuilder subscription for new hosted sends; prior drafts and history may remain visible
On this page
Before you start
Data, sources, and access to prepare
- Your final contact details
- A public http(s) logo URL if using a logo
Understand user scope and supported delivery
| Property | Behavior |
|---|---|
| Owner | The signature belongs to the signed-in user, not the entire company. |
| Enabled state | A saved signature is appended only when Include signature is enabled. |
| Sanitization | The server removes unsafe HTML and rejects unsafe logo URLs. |
| Preview source | The preview renders the server’s saved copy, not unsaved text. |
| Hosted message scope | Backend composition appends the enabled signature to supported hosted blasts, automation emails, and NDA invitation messages. |
Verify each sender separately
One teammate’s signature does not configure another teammate. Each sender should save and inspect their own preview.
Hosted signature verification path
The saved server copy, enabled state, and hosted composer determine what is appended to a supported message.
Basic HTML and logo URL
Prepared by the signed-in sender
Server sanitization
Unsafe markup and URLs are removed or rejected
Saved preview
Shows the stored server copy
Hosted message
Appends only when enabled
- Basic HTML and logo URLServer sanitization
- Server sanitizationSaved preview
- Saved previewHosted message
Prepare compatible content
| Field | Requirement | What it means | Format | Units | Save behavior | Downstream effect |
|---|---|---|---|---|---|---|
| Signature HTML | Recommended | Concise contact and company block using basic HTML | Basic HTML only | Characters | Stored for the signed-in user when Save signature succeeds. | Supplies the sanitized signature block appended to eligible Email Blasts when enabled. |
| Logo URL | Optional | Optional publicly reachable logo image | Public http:// or https:// URL | Not applicable | Stored with the signed-in user’s signature when Save signature succeeds. | Lets supported email clients request the public logo when the signature renders. |
| Include signature | Required | Controls whether the saved signature is appended | On or off toggle | Not applicable | Stored with the signed-in user’s signature when Save signature succeeds. | Determines whether the saved signature is appended to eligible Email Blasts. |
Required means the field is needed to complete or support this workflow. Some screens allow a draft to save before every required item is complete. The steps and troubleshooting call out controls the product actively blocks.
Save and inspect the server copy
- 1
Open the editor
Settings > Email sending > Email signature
Review the current enabled state, HTML, logo URL, and saved preview.
Expected result: You know what is currently stored for your user.
If this does not happen: If loading fails, retry settings before replacing content.
- 2
Enter signature content
Email signature editor
Add concise basic HTML and an optional public http(s) logo URL.
Expected result: The draft contains only intended business identity and safe public resources.
If this does not happen: If a logo exists only on a local computer or private drive, publish it to an approved public HTTPS location first.
- 3
Choose the enabled state
Email signature editor > Include signature
Set Include signature to the intended state.
Expected result: The draft reflects whether the signature will be included.
If this does not happen: Leave the signature disabled when the saved content should not be used.
- 4
Save the signature
Email signature editor > Save signature
Select Save signature once.
Expected result: A success or sanitization warning appears and the server copy refreshes.
If this does not happen: If everything was removed or the logo dropped, simplify unsafe HTML or correct the URL before saving again.
- 5
Inspect Saved preview
Email signature > Saved preview
Compare the rendered server copy with the intended signature.
Expected result: The preview shows exactly the sanitized content available to hosted composition.
If this does not happen: Do not rely on the unsaved text area. Correct and save until the preview is accurate.
Resolve stripped or stale signatures
Everything in the signature was removed
Likely cause: The submitted HTML contained only unsafe or unsupported markup.
- Replace it with basic text, links, line breaks, and simple supported formatting.
- Save again.
- Verify Saved preview.
The logo URL was dropped
Likely cause: The value is not a valid http(s) URL.
- Use a complete public HTTPS URL.
- Confirm it loads without authentication.
- Save and verify the preview image.
A previous signature appeared in a held-send recovery
Likely cause: Held operations bind composed content and a changed signature can cause a replay divergence rather than silently sending changed content.
- Read the returned recovery message.
- Do not force-resend the old operation.
- Create a new reviewed send only when the application clearly tells you the prior operation is terminal and safe.
A teammate still has the wrong signature
Likely cause: Signatures are per user.
- Have that teammate open their own Email sending settings.
- Save and verify their server preview.
- Do not share login credentials to configure it.
Final verification
- Email signature editor: The draft contains only intended business identity and safe public resources.
- Email signature editor > Include signature: The draft reflects whether the signature will be included.
- Email signature editor > Save signature: A success or sanitization warning appears and the server copy refreshes.
- Email signature > Saved preview: The preview shows exactly the sanitized content available to hosted composition.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.