Email

Workspace-wide email footer appended to every outbound message.

Intermediate
2 min read

Email

Workspace-wide defaults for outbound email. Per-inbox settings (from-address, signature, routing) live on each inbox — see Email Inboxes.

Go to SettingsWorkspaceEmail.

A rich-HTML footer appended to every outbound email sent from this workspace. Typically used for:

  • Contact information ("Reply to this email or visit acme.com/contact")
  • Compliance disclosures (HIPAA, unsubscribe instructions)
  • Branding (logo links, social handles)
  • Legal disclaimers

Template variables

Two template variables are available inside the footer:

VariableRenders
{{workspace.name}}The current workspace's name
{{assistant.name}}The name of the assistant sending the email

Allowed HTML

The footer is sanitised on save. Only the following tags survive:

  • <p>, <br>, <a> (with href and title), <strong>, <em>, <ul>, <li>

Any other tag is silently stripped on save and its inner text preserved.

Allowed link protocols: http://, https://, mailto:. Other protocols (including javascript:) are removed from href attributes.

Inline event handlers (onclick, onerror, etc.) are stripped on save.

Length limit

2000 characters max. Saving a longer footer returns an error — shorten it before retrying. The system won't truncate automatically because that could leave a half-open tag.

Tips

  • Keep it short. Most clients display long footers awkwardly on mobile. Aim for a few short lines plus a contact link.
  • Test with a real email send. The editor preview is approximate; some clients render <a> tags differently than the editor shows.
  • Use template variables instead of hard-coded names. {{workspace.name}} keeps the footer correct if the workspace gets renamed; hard-coded text doesn't.
  • HIPAA disclosures belong here. A workspace-wide footer is the right place for "This email may contain PHI" boilerplate so every outbound message carries it consistently.