Skip to main content

Email

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

Go to Settings → Workspace → Email.

Default reply-to address​

Where replies go when Gravity Rail sends email on your workspace's behalf but not from one of your inboxes — membership confirmations, billing notices and similar automated messages.

ChoiceWhat happens when a recipient hits Reply
Platform reply-to (noreply@gravityrail.net)Replies go here — this is not the visible From. The address can receive mail, but nobody reads it.
An inboxThe reply arrives in that inbox and starts its workflow, exactly like any other email to it.

Pick an inbox if you want replies to these messages to reach a person or an agent. This is the single most common surprise in automated email: a recipient replies to a receipt, and without an inbox selected that reply goes nowhere.

Email sent from an inbox is unaffected — it already replies to that inbox, because that inbox is the sender.

If the inbox you selected is later deleted, the setting falls back to the default rather than breaking the send.

What automated email always includes​

Regardless of your footer, email Gravity Rail sends on your behalf carries a short platform line with a Privacy Policy link, and — when the recipient is a member of this workspace — a link to their own notification preferences. This is added on top of your footer, not instead of it: writing a custom footer does not remove the compliance links.

So don't repeat them in your footer. A footer that also links the privacy policy or preferences shows the recipient each link twice — and in the plain-text version the duplicate arrives as a bare label with no link at all, because stripping the link tag drops its address. Put {{preferences_url}} in an inbox footer instead (Email Inboxes): mail sent from an inbox gets no platform line, so there it is the recipient's only route to their settings.

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

This footer is the workspace-wide default. An individual inbox can override it with its own footer — see Email Inboxes. An inbox footer replaces this one for mail sent from that inbox; it is not added on top of it.

Template variables​

VariableRenders
{{workspace.name}}The current workspace's name
{{assistant.name}}The name of the assistant sending the email
{{preferences_url}}A link to the recipient's own notification preferences
{{unsubscribe_url}}A one-click opt-out link

{{preferences_url}} and {{unsubscribe_url}} are only filled in for email sent to a member of this workspace. In a reply to an outside correspondent they are removed rather than left as a broken link — an outsider has no preferences page here, and should never receive a member's opt-out link.

If your footer does not include {{unsubscribe_url}}, an unsubscribe line is added automatically: the opt-out has to work, so it is never dropped. There is no equivalent automatic preferences line — add {{preferences_url}} yourself if you want one.

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.
  • Point the reply-to at a monitored inbox before a launch. Automated email goes out at the least convenient moment to discover nobody is receiving the replies.