Email templates: custom sender address

Overview

By default, Kompass sends notification email from a single system address, "Kompass BMS" <notifications@…> . That address uses a shared Kompass sending domain that we keep warmed so mail reaches the inbox reliably. It is not a per-account subdomain.

From May 2026 you can override the From address on individual email templates, so a particular type of email (invoices, for example) can come from a different address such as a team inbox or the relevant person.

Sending from your own domain

Kompass will only send from a domain it is authorised for. To send invoices (or any other email) from your own domain, for example [email protected] , that domain has to be verified with Kompass first.

Contact Kompass support to set up your domain as a sending domain. This involves adding a few DNS records (SPF, DKIM, and DMARC) so that Kompass is authorised to send on your behalf and the mail passes authentication.
Until your domain is verified, any From address on that domain is ignored and the email falls back to the default system address instead.

Use cases

Send invoice emails from [email protected] rather than the default system address.
Send leave approval notifications from the approver's own email so replies go directly to them.
White-label notifications for a specific organisation in a multi-org deployment.

Configuring a template

Open the Django admin at /admin/.
Navigate to the relevant email templates section, for example Clients → Invoice email templates, Leave → Email templates, or Tasks → Email templates. Each app has its own templates, so change the ones you need in each place.
Open the template you want to customise.
In the Sender template field, enter the address you want the email to come from. You can use a plain address or a "Display name" <address> pair. The field's help text lists the domains your account is currently authorised to send from.

Examples:

[email protected]
"Accounts Team" <[email protected]>
"{{ decided_by.name }}" <{{ decided_by.email }}>

The field is itself a Jinja2 template rendered at send time with the same context as the email body, so you can reference the user, project, client, or other objects available to that template type. The default value is {{ kompass_notification_sender }} , which resolves to the standard system address. Leave it as that (or blank) to keep the default behaviour.

Validation and fallback

When you save a template, Kompass checks that the Sender template renders to a valid email address. An invalid one is rejected in the admin, so you cannot save a broken template.
At send time, if the rendered value is empty, not a valid address, or on a domain your account is not authorised for, the email quietly falls back to the default system address and the event is logged for review. Mail is never sent unauthenticated.

Reply-To

Reply-To is managed by Kompass and is not set on individual templates.

System emails such as password resets and invitations use a monitored Kompass support address for replies.
Configurable notifications reply to their own From address, so when you set a custom sender, replies go to that address.