Semaphor

Branded Report Emails

Put your organization's name, logo, and standing copy on every scheduled report and Briefing email

Overview

Scheduled reports and Briefings arrive by email. With email branding, those emails carry your organization's name in the From line, your logo, your accent color, and standing intro and footer copy, so recipients recognize who the report is from. You set it up once in Brand Studio and every email inherits it on its next send.

Open Brand Studio from the sidebar and switch to the Email reports tab. Email branding is available to organization admins.

Until you set it up, emails go out with the Semaphor default look: sent as Semaphor from the platform address, with no logo.

What you can configure

Sender

FieldWhat it does
From nameThe sender name recipients see in their inbox. Starts as your organization name. Up to 80 characters, no quotes or angle brackets.
From addressRead-only. Emails are sent from the platform address, noreply@semaphor.cloud on Semaphor Cloud, unless you set up a custom sending domain.
Reply-toOptional. Where replies go instead of the no-reply address.
BCCOptional. A mailbox that receives a copy of every report email. See BCC and recipient privacy.

Assets

FieldWhat it does
Organization logoEmails use the same organization logo as the rest of Semaphor. Upload or remove it here or in Organization settings. See Logo.
Accent colorColors the sender name in the email header and the optional button. Leave it empty to use the primary color from your Brand Studio appearance. Enter a six-digit hex value such as #1a6ef4 to override it.
App URLOptional. An HTTPS link to your own application. When set, the email includes a button that opens it.
Button labelThe text on that button. Starts as Open app and is editable once an App URL is present. Up to 40 characters.

Template

FieldWhat it does
IntroStanding copy at the top of every email, above the message written by whoever scheduled the report. Up to 2,000 characters.
FooterStanding copy at the bottom of every email. Up to 1,000 characters.

Both fields accept two variables. Use the Insert chips under each field, or type them:

VariableFills in
{{report.name}}The name of the report or Briefing being delivered
{{org.name}}Your organization name

Only these two variables are recognized. The subject line is never variable-filled; it is the report name that the author gave the schedule.

Defaults

A new setup starts from these values so you can see what is customizable:

From name:    <your organization name>
Intro:        Hello,

              Your {{report.name}} is ready.
Footer:       Sent by {{org.name}}. You are receiving this email because you are subscribed to {{report.name}}.
Button label: Open app

How the email is put together

Every branded email uses one compact layout, in this order:

  1. Your logo, when one is usable, and the From name in your accent color
  2. Your intro
  3. The message written by whoever scheduled the report, or the default message when they left it blank
  4. Download links for large attachments, when present
  5. The optional button that opens your App URL
  6. Your footer

The subject, the author's message, the recipients, and the attached PDF or CSV are unchanged. Branding is applied when the email is sent, so people who schedule reports do not choose anything: the schedule panel is the same for organization users and tenant users.

Emails reuse the logo configured for your organization. Uploading or removing it from Email reports changes the same organization logo managed in Organization settings; there is no separate email-only logo. Every email picks up the change on its next send.

Email clients render a narrower set of image formats than browsers. The logo appears in email when it is a PNG, JPEG, or GIF served over HTTPS. In two cases the email shows the From name as text instead of a logo:

  • No organization logo is configured. Upload a PNG, JPEG, or GIF from Email reports or Organization settings.
  • The stored logo is not email-compatible, for example an SVG. Email falls back to the From name until an admin replaces it with a PNG, JPEG, or GIF.

The preview in the tab reflects the same rule, so what you see is what recipients get.

BCC and recipient privacy

When you set a BCC mailbox, it receives a hidden copy of every report email, with the same attachments. Use it to keep an archive or to let a shared inbox see everything that goes out.

  • Recipients never see the BCC address. It is not written into the email headers they receive.
  • One copy is sent per recipient message. A report addressed to five people produces five hidden copies, one for each recipient's message.
  • When a recipient is the BCC mailbox itself, no extra copy is sent.
  • The test email includes the BCC copy too, so you can confirm the mailbox receives it.

Leave BCC empty if you do not need a copy.

Preview and test

The right side of the tab shows the email as it will arrive, built from a sample report named Weekly revenue report. Switch between desktop and mobile widths to check both. The preview updates as you type; while a field is invalid it keeps showing the last valid version and says so.

Send test email sends that exact sample to your own address, with your BCC copied when one is set. It never goes to anyone else and has no attachment. Test emails are limited to three every five minutes.

Saving and removing

Save stores the branding for the whole organization. Changes apply to the next send of every scheduled report and Briefing; emails already sent are unaffected. Leaving the tab with unsaved changes prompts you first.

Remove branding returns every email to the Semaphor default look. Confirm the prompt, and the next send goes out as Semaphor with no logo, intro, footer, reply-to, or BCC. You can set branding up again at any time.

Needs repair

If the tab reports that the saved branding could not be read, scheduled emails are failing rather than going out unbranded. Review the fields, which start from the defaults, and save again.

Self-hosted deployments

Branded email is delivered by the report scheduler stack, through either Amazon SES or the bundled Resend provider. Deploy the scheduler release that supports branding before enabling it in the app; see Reports, Briefings, and Scheduled Delivery for the provider settings and deployment order.

On this page